Skip to content

fix(docs): Replace hardcoded main-branch references with DOCS_VAR_CLP_GIT_REF.#1885

Merged
kirkrodrigues merged 2 commits into
y-scope:mainfrom
kirkrodrigues:make-links-version-agnostic
Jan 19, 2026
Merged

fix(docs): Replace hardcoded main-branch references with DOCS_VAR_CLP_GIT_REF.#1885
kirkrodrigues merged 2 commits into
y-scope:mainfrom
kirkrodrigues:make-links-version-agnostic

Conversation

@kirkrodrigues

@kirkrodrigues kirkrodrigues commented Jan 19, 2026

Copy link
Copy Markdown
Member

Description

In the new Kubernetes guide (added in #1827):

  • The Helm chart we reference and ask users to download is from main, which can go out of sync with a specific release.
  • There's an unused link reference.

This PR addresses both issues by using DOCS_VAR_CLP_GIT_REF:

  • The git clone command we ask users to use now includes --branch DOCS_VAR_CLP_GIT_REF so that the specific reference is cloned.
  • The link to the Helm chart now uses DOCS_VAR_CLP_GIT_REF instead of main.

Checklist

  • The PR satisfies the contribution guidelines.
  • This is a breaking change and that has been indicated in the PR title, OR this isn't a
    breaking change.
  • Necessary docs have been updated, OR no docs need to be updated.

Validation performed

  • task docs:serve
  • Validated the rendered docs linked to blobs on the current git reference (main).

Summary by CodeRabbit

  • Documentation
    • Updated Kubernetes deployment guide to use branch-specific repository clone instructions.
    • Updated Helm chart documentation references to point to branch-specific paths.
    • Updated Presto setup guide to use branch-specific repository clone instructions.

✏️ Tip: You can customize this high-level summary in your review settings.

@kirkrodrigues kirkrodrigues requested a review from a team as a code owner January 19, 2026 11:56
@coderabbitai

coderabbitai Bot commented Jan 19, 2026

Copy link
Copy Markdown
Contributor

Walkthrough

Repository documentation updates replace hardcoded main-branch references with a branch-specific variable DOCS_VAR_CLP_GIT_REF for clone commands and Helm/chart links in two user guide files.

Changes

Cohort / File(s) Summary
Kubernetes deployment docs
docs/src/user-docs/guides-k8s-deployment.md
Replaced git clone https://github.com/y-scope/clp.git with git clone --branch DOCS_VAR_CLP_GIT_REF https://github.com/y-scope/clp.git; updated CLP Helm chart and values hyperlinks to use DOCS_VAR_CLP_GIT_REF branch path.
Presto setup docs
docs/src/user-docs/guides-using-presto.md
Replaced two git clone commands with branch-specific clones using --branch DOCS_VAR_CLP_GIT_REF to fetch the repository at the specified ref.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately reflects the main change: replacing hardcoded main-branch references with a variable across documentation files.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a 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.

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In `@docs/src/user-docs/guides-k8s-deployment.md`:
- Around line 586-589: Replace the absolute GitHub URL assigned to the link
reference [clp-helm-chart] with a relative repository path so the docs reference
the in-repo Helm chart at the same commit; locate the link definition for
[clp-helm-chart] and change its target from
"https://github.com/y-scope/clp/tree/DOCS_VAR_CLP_GIT_REF/tools/deployment/package-helm"
to a relative path like "tools/deployment/package-helm/" (or the
doc-build-supported relative syntax) so the docs point to the in-repo chart
instead of a hardcoded GitHub URL.

Comment on lines 586 to +589
[aks]: https://azure.microsoft.com/en-us/products/kubernetes-service
[api-server]: guides-using-the-api-server.md
[Cilium]: https://cilium.io/
[clp-helm-chart]: https://github.com/y-scope/clp/tree/main/tools/deployment/package-helm
[clp-helm-chart-values]: https://github.com/y-scope/clp/blob/main/tools/deployment/package-helm/values.yaml
[clp-helm-chart]: https://github.com/y-scope/clp/tree/DOCS_VAR_CLP_GIT_REF/tools/deployment/package-helm

@coderabbitai coderabbitai Bot Jan 19, 2026

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.

🧹 Nitpick | 🔵 Trivial

Prefer a relative repo path for the Helm chart link.

The chart is in-repo; using a relative path keeps docs and referenced files on the same commit and avoids hardcoded GitHub URLs. Based on learnings, consider replacing the GitHub link with a relative path to tools/deployment/package-helm/ if the docs build supports it.

Based on learnings, ...

🤖 Prompt for AI Agents
In `@docs/src/user-docs/guides-k8s-deployment.md` around lines 586 - 589, Replace
the absolute GitHub URL assigned to the link reference [clp-helm-chart] with a
relative repository path so the docs reference the in-repo Helm chart at the
same commit; locate the link definition for [clp-helm-chart] and change its
target from
"https://github.com/y-scope/clp/tree/DOCS_VAR_CLP_GIT_REF/tools/deployment/package-helm"
to a relative path like "tools/deployment/package-helm/" (or the
doc-build-supported relative syntax) so the docs point to the in-repo chart
instead of a hardcoded GitHub URL.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

We're linking to a directory, so it doesn't seem to work with sphinx.

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.

@kirkrodrigues, thank you for the clarification! You're absolutely right—Sphinx doesn't support relative paths for directory links in the same way it does for files. Using the GitHub URL with DOCS_VAR_CLP_GIT_REF is the appropriate solution here, as it still keeps the link version-agnostic (which was the goal of this PR) while working within Sphinx's limitations.

The approach you've taken accomplishes the same goal as using relative paths: ensuring the documentation links point to resources at the correct version/commit.

ヾ(•ω•`)o


✏️ Learnings added
Learnt from: kirkrodrigues
Repo: y-scope/clp PR: 1885
File: docs/src/user-docs/guides-k8s-deployment.md:586-589
Timestamp: 2026-01-19T12:06:17.530Z
Learning: In the y-scope/clp project documentation built with Sphinx, relative paths work for linking to files within the repository, but directory links require GitHub URLs. When linking to directories (e.g., the Helm chart at tools/deployment/package-helm/), use GitHub URLs with DOCS_VAR_CLP_GIT_REF to keep them version-agnostic.

Note: Learnings are effective only in the context of similar code segments. To apply general coding guidelines, please configure review instructions. You can manage existing learnings in the app.


🧠 Learnings used
Learnt from: junhaoliao
Repo: y-scope/clp PR: 1818
File: tools/deployment/package-helm/templates/configmap.yaml:12-12
Timestamp: 2025-12-19T05:03:42.629Z
Learning: In the y-scope/clp Helm chart, the `api_server.host` configuration field in the ConfigMap (tools/deployment/package-helm/templates/configmap.yaml) is unused because no other k8s internal services need to reach the API server—it's only accessed from outside the cluster via NodePort.

Learnt from: Bill-hbrhbr
Repo: y-scope/clp PR: 1261
File: docs/src/dev-guide/components-core/manylinux-2-28-deps-install.md:24-24
Timestamp: 2025-08-25T06:32:48.313Z
Learning: In the CLP project documentation, when linking to scripts or other files within the repository, use relative paths (e.g., components/core/tools/scripts/...) rather than commit-pinned GitHub URLs to ensure docs and referenced files always belong to the same commit and stay synchronized.

Learnt from: junhaoliao
Repo: y-scope/clp PR: 1466
File: .github/workflows/clp-rust-checks.yaml:14-15
Timestamp: 2025-10-22T21:14:12.225Z
Learning: Repository y-scope/clp: In GitHub Actions workflows (e.g., .github/workflows/clp-rust-checks.yaml), YAML anchors/aliases are acceptable and preferred to avoid duplication; if actionlint flags an alias node (e.g., on push.paths) as an error, treat it as a tool limitation and do not require inlining unless the team asks to silence the warning.

Learnt from: junhaoliao
Repo: y-scope/clp PR: 0
File: :0-0
Timestamp: 2025-10-22T21:02:31.113Z
Learning: Repository y-scope/clp: Maintain deterministic CI/builds for Rust; add a check to verify Cargo.lock is in sync with Cargo.toml without updating dependencies (non-mutating verification in clp-rust-checks workflow).

Learnt from: junhaoliao
Repo: y-scope/clp PR: 1405
File: components/clp-package-utils/pyproject.toml:5-15
Timestamp: 2025-10-13T03:24:35.074Z
Learning: In the y-scope/clp repository, the Python 3.9 to 3.10 version requirement change was intentionally deferred to a separate PR (after PR `#1405`) to reduce review effort, as decided in an offline discussion between junhaoliao and kirkrodrigues.

junhaoliao
junhaoliao previously approved these changes Jan 19, 2026

@junhaoliao junhaoliao left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

shall we update this one too?

git clone https://github.com/y-scope/clp.git

otherwise, the PR is good to go

@junhaoliao

Copy link
Copy Markdown
Member

the current title doesn't fully reflect the change in the doc link (though i agree technically it's still dealing with the git branch reference). would this title be more clear and accurate?

fix(docs): Avoid specific hardcoded main branch with `DOCS_VAR_CLP_GIT_REF` in k8s deployment guide.

@kirkrodrigues kirkrodrigues changed the title fix(docs): Replace specific git references with DOCS_VAR_CLP_GIT_REF. fix(docs): Replace hardcoded main-branch references with DOCS_VAR_CLP_GIT_REF. Jan 19, 2026
@kirkrodrigues

Copy link
Copy Markdown
Member Author
fix(docs): Avoid specific hardcoded main branch with `DOCS_VAR_CLP_GIT_REF` in k8s deployment guide.

How about the new title?

@kirkrodrigues kirkrodrigues merged commit 1459d66 into y-scope:main Jan 19, 2026
10 checks passed
@kirkrodrigues kirkrodrigues deleted the make-links-version-agnostic branch January 19, 2026 15:46
junhaoliao pushed a commit to junhaoliao/clp that referenced this pull request May 17, 2026
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