Skip to content

DOC-17059: Remove/replace cockroach links in YAML/data files#23304

Merged
ebembi-crdb merged 7 commits into
mainfrom
update-yaml-data-links
May 29, 2026
Merged

DOC-17059: Remove/replace cockroach links in YAML/data files#23304
ebembi-crdb merged 7 commits into
mainfrom
update-yaml-data-links

Conversation

@ebembi-crdb
Copy link
Copy Markdown
Contributor

Summary

  • Updates 10 non-markdown files (api-spec.json, menus.yml, 8 metrics YAMLs)
  • Shortens GitHub issue URLs in metrics YAML files
  • Removes GitHub navigation links from menus.yml

This is PR 5 of 10 splitting #23256 into reviewable chunks.

Jira: DOC-17059

Test plan

  • Verify metrics pages still render correctly with shortened issue URLs
  • Verify navigation menus render correctly without GitHub links
  • Run local Jekyll build

🤖 Generated with Claude Code

Update 10 non-markdown files: shorten GitHub issue URLs in metrics
YAML files, remove GitHub navigation links from menus.yml, and update
API spec references.

Part of DOC-17059.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 12, 2026

Files changed:

  • src/api/api-spec.json
  • src/current/_data/menus.yml
  • src/current/_data/v24.2/metrics/child-metrics.yml
  • src/current/_data/v24.3/metrics/child-metrics.yml
  • src/current/_data/v25.1/metrics/multi-dimensional-metrics.yml
  • src/current/_data/v25.2/metrics/multi-dimensional-metrics.yml
  • src/current/_data/v25.3/metrics/multi-dimensional-metrics.yml
  • src/current/_data/v25.4/metrics/multi-dimensional-metrics.yml
  • src/current/_data/v26.1/metrics/multi-dimensional-metrics.yml
  • src/current/_data/v26.2/metrics/multi-dimensional-metrics.yml
  • src/current/_data/v26.3/metrics/multi-dimensional-metrics.yml

@netlify
Copy link
Copy Markdown

netlify Bot commented May 12, 2026

Deploy Preview for cockroachdb-interactivetutorials-docs canceled.

Name Link
🔨 Latest commit f6b01ee
🔍 Latest deploy log https://app.netlify.com/projects/cockroachdb-interactivetutorials-docs/deploys/6a19b31be394190008040d79

@netlify
Copy link
Copy Markdown

netlify Bot commented May 12, 2026

Deploy Preview for cockroachdb-api-docs canceled.

Name Link
🔨 Latest commit f6b01ee
🔍 Latest deploy log https://app.netlify.com/projects/cockroachdb-api-docs/deploys/6a19b31b22439a000810ffd6

@netlify
Copy link
Copy Markdown

netlify Bot commented May 12, 2026

Netlify Preview

Name Link
🔨 Latest commit f6b01ee
🔍 Latest deploy log https://app.netlify.com/projects/cockroachdb-docs/deploys/6a19b31b56eec200092129c5
😎 Deploy Preview https://deploy-preview-23304--cockroachdb-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link
Copy Markdown
Contributor

@rmloveland rmloveland left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

left a couple comments about removing references to things entirely vs just renaming link targets

also had a question / FYI for @kikiya re: package name policy (assume it's fine? but flagging because "never assume")

Comment thread src/api/api-spec.json Outdated
},
"global_reads": {
"description": "Whether transactions operating over the range(s)\nshould be configured to provide non-blocking behavior, meaning that reads\ncan be served consistently from all replicas and do not block on writes. In\nexchange, writes get pushed into the future and must wait on commit to\nensure linearizability. For more, see:\nhttps://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20200811_non_blocking_txns.md",
"description": "Whether transactions operating over the range(s)\nshould be configured to provide non-blocking behavior, meaning that reads\ncan be served consistently from all replicas and do not block on writes. In\nexchange, writes get pushed into the future and must wait on commit to\nensure linearizability. For more, see:\nhttps://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20200811_non_blocking_txns.md",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please remove the "for more ..." line and the link, we don't need to pull that file into the docs repo

Comment thread src/api/api-spec.json Outdated
"properties": {
"constraints": {
"description": "Constrains which stores the replicas can be stored on. The\norder in which the constraints are stored is arbitrary and may change.\nhttps://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20160706_expressive_zone_config.md#constraint-system",
"description": "Constrains which stores the replicas can be stored on. The\norder in which the constraints are stored is arbitrary and may change.\nhttps://github.com/cockroachdb/docs/blob/main/src/current/files/cockroach/docs/RFCS/20160706_expressive_zone_config.md#constraint-system",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please remove the http link entirely, we don't need to pull that file into our repo

Comment thread src/api/api-spec.json Outdated
"format": "int32",
"title": "A custom type for a range replica ID.",
"x-go-package": "github.com/cockroachdb/cockroach/pkg/roachpb"
"x-go-package": "cockroachdb/cockroach/pkg/roachpb"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this seems fine to me, but i don't have enough context on what this file even does or how it's used

also, i "assume" it's fine to still refer to Go packages at this level of specificity - seems unavoidable? but ultimately idk

cc @kikiya FYI since you may have more context on this from a policy POV

@@ -1,6 +1,6 @@
# child-metrics.yml is a manually curated file of metrics that are included in the Child Metrics.
# The metrics are in the order of appearance in the comment:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please delete this whole "the metrics are in the order of appearance in the comment ..." part

@@ -1,6 +1,6 @@
# child-metrics.yml is a manually curated file of metrics that are included in the Child Metrics.
# The metrics are in the order of appearance in the comment:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same as other comment, please delete this whole "the metrics are in the order of appearance ..." section including the issue reference

@@ -1,6 +1,6 @@
# multi-dimensional-metrics.yml is a manually curated file of metrics that are included in the Multi-Dimensional Metrics page.
# The metrics are in the order of appearance in the comment:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same as other comment, please delete this whole "the metrics are in the order of appearance ..." section including the issue reference

@@ -1,6 +1,6 @@
# multi-dimensional-metrics.yml is a manually curated file of metrics that are included in the Multi-Dimensional Metrics page.
# The metrics are in the order of appearance in the comment:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same as other comment, please delete this whole "the metrics are in the order of appearance ..." section including the issue reference

@@ -1,6 +1,6 @@
# multi-dimensional-metrics.yml is a manually curated file of metrics that are included in the Multi-Dimensional Metrics page.
# The metrics are in the order of appearance in the comment:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same as other comment, please delete this whole "the metrics are in the order of appearance ..." section including the issue reference

@@ -1,6 +1,6 @@
# multi-dimensional-metrics.yml is a manually curated file of metrics that are included in the Multi-Dimensional Metrics page.
# The metrics are in the order of appearance in the comment:
# https://github.com/cockroachdb/cockroach/issues/124343#issuecomment-2117886012
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same as other comment, please delete this whole "the metrics are in the order of appearance ..." section including the issue reference

@@ -1,6 +1,6 @@
# multi-dimensional-metrics.yml is a manually curated file of metrics that are included in the Multi-Dimensional Metrics page.
# The metrics are in the order of appearance in the comment:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same as other comment, please delete this whole "the metrics are in the order of appearance ..." section including the issue reference

- Remove "metrics are in order of appearance in the comment" lines
  and cockroach#124343 references from all metrics YAML files
- Remove RFC URLs from api-spec.json descriptions instead of
  redirecting to vendored paths
- Revert x-go-package changes: these are Go module import paths
  (not GitHub URLs) and should retain their github.com/cockroachdb/
  prefix

Addresses review feedback from @rmloveland.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@ebembi-crdb
Copy link
Copy Markdown
Contributor Author

All review comments have been addressed:

  1. Metrics YAML files: Removed the orphaned comment lines (# The metrics are in the order of appearance in the comment: and # cockroach#124343) from 8 metrics YAML files across v24.2–v26.2.

  2. API spec RFC URLs: Removed 2 RFC URL references from src/api/api-spec.json description fields (zone config constraints and global_reads).

  3. x-go-package fields reverted: Restored all 62 x-go-package values back to "github.com/cockroachdb/..." — these are Go module import paths, not GitHub URLs, so they should not have been modified.

Comment thread src/api/api-spec.json
}
},
"x-go-package": "cockroachdb/cockroach/pkg/server/serverpb"
"x-go-package": "github.com/cockroachdb/cockroach/pkg/server/serverpb"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ebembi-crdb my comment was definitely not asking for this to be added back, i was saying it seems fine (aka LGTM), just pinged Kiki for context/awareness

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah ok i see the explanation in your comment - defer to your expertise on that - please merge at will

Copy link
Copy Markdown
Contributor

@rmloveland rmloveland left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM except i don't think we should add back the github.com stuff, see my comment - once that is removed again this is ready to merge IMO (edit: pls ignore per this convo merge at your convenience)

@rmloveland
Copy link
Copy Markdown
Contributor

@ebembi-crdb before merging this can you please make sure to port it forward to v26.3 as well? looks like #23371 was merged in the meantime

@ebembi-crdb ebembi-crdb enabled auto-merge May 27, 2026 14:35
ebembi-crdb and others added 5 commits May 27, 2026 20:06
Remove orphaned cockroach issue comment lines from v26.3
multi-dimensional-metrics.yml, matching the same changes already made
for v24.2–v26.2.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@ebembi-crdb ebembi-crdb merged commit 9846d1a into main May 29, 2026
5 checks passed
@ebembi-crdb ebembi-crdb deleted the update-yaml-data-links branch May 29, 2026 15:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants