fix: revert "ci: remove redundant docs workflow"#856
Conversation
This reverts commit b18627f.
📝 WalkthroughWalkthroughA new GitHub Actions workflow file has been added to automatically validate documentation on pull requests. The workflow triggers on changes to documentation, README, dependencies, or the workflow itself, installing dependencies and building Sphinx documentation in strict mode with a 10-minute execution limit. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
ericksoa
left a comment
There was a problem hiding this comment.
LGTM — straightforward revert restoring the docs build validation on PRs.
There was a problem hiding this comment.
🧹 Nitpick comments (2)
.github/workflows/docs.yaml (2)
39-40: Use--lockedflag to enforce reproducible CI builds.Line 40 should explicitly enforce that the lockfile is up to date and prevent it from being modified during installation. Use
--lockedto fail ifuv.lockis out of sync withpyproject.toml, ensuring deterministic behavior in CI.Suggested change
- name: Install doc dependencies - run: uv sync --group docs + run: uv sync --group docs --locked🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.github/workflows/docs.yaml around lines 39 - 40, Update the "Install doc dependencies" step so the install command uses the --locked flag to enforce the lockfile; specifically modify the command referenced ("uv sync --group docs") to "uv sync --group docs --locked" so CI fails if uv.lock is out of sync with pyproject.toml and prevents lockfile changes during the run.
29-37: Pin external actions to immutable SHAs for stronger supply-chain integrity.Lines 29, 32, and 37 use floating major version tags. SHA pinning (e.g.,
actions/checkout@692973e3d937129bcbf40652eb9f2f61becf3332 # v6.2.0) is GitHub's recommended best practice for supply-chain security, as version tags are mutable and can be updated to point to malicious code. Pinning to commit SHAs prevents this risk, particularly for third-party actions likeastral-sh/setup-uv@v7. Consider adding comments with the corresponding version tag to allow automated tools like Dependabot to track updates.Note: This pattern appears across multiple workflows in the repository; consider standardizing as part of a repo-wide security hardening effort.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.github/workflows/docs.yaml around lines 29 - 37, The workflow uses floating major-version tags for external actions (actions/checkout@v6, actions/setup-python@v6, astral-sh/setup-uv@v7); replace each action reference with the corresponding immutable commit SHA (pin to the action's full commit hash) and optionally keep the human-readable tag as a comment (e.g., "# v6.2.0") so Dependabot/maintainers can track updates; apply the same SHA-pinning pattern for any other workflows that reference third-party actions to harden supply-chain security.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In @.github/workflows/docs.yaml:
- Around line 39-40: Update the "Install doc dependencies" step so the install
command uses the --locked flag to enforce the lockfile; specifically modify the
command referenced ("uv sync --group docs") to "uv sync --group docs --locked"
so CI fails if uv.lock is out of sync with pyproject.toml and prevents lockfile
changes during the run.
- Around line 29-37: The workflow uses floating major-version tags for external
actions (actions/checkout@v6, actions/setup-python@v6, astral-sh/setup-uv@v7);
replace each action reference with the corresponding immutable commit SHA (pin
to the action's full commit hash) and optionally keep the human-readable tag as
a comment (e.g., "# v6.2.0") so Dependabot/maintainers can track updates; apply
the same SHA-pinning pattern for any other workflows that reference third-party
actions to harden supply-chain security.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 0a9b1e74-6855-42e5-8448-4e9a6b7185e5
📒 Files selected for processing (1)
.github/workflows/docs.yaml
* fix(ci): post docs preview comment with explicit PR number The workflow_run context has no github.event.pull_request.number, so rossjrw/pr-preview-action's internal sticky comment silently skips posting. Disable its built-in comment and add an explicit marocchino/sticky-pull-request-comment step that passes the PR number from the artifact metadata. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * test: test * fix: remove test * ci: revert "revert ci: remove redundant docs workflow (#725)" (#856) This reverts commit 36fa334. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Co-authored-by: Miyoung Choi <miyoungc@nvidia.com>
This reverts commit b18627f.
* fix(ci): post docs preview comment with explicit PR number The workflow_run context has no github.event.pull_request.number, so rossjrw/pr-preview-action's internal sticky comment silently skips posting. Disable its built-in comment and add an explicit marocchino/sticky-pull-request-comment step that passes the PR number from the artifact metadata. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * test: test * fix: remove test * ci: revert "revert ci: remove redundant docs workflow (NVIDIA#725)" (NVIDIA#856) This reverts commit 36fa334. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Co-authored-by: Miyoung Choi <miyoungc@nvidia.com>
This reverts commit b18627f.
* fix(ci): post docs preview comment with explicit PR number The workflow_run context has no github.event.pull_request.number, so rossjrw/pr-preview-action's internal sticky comment silently skips posting. Disable its built-in comment and add an explicit marocchino/sticky-pull-request-comment step that passes the PR number from the artifact metadata. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * test: test * fix: remove test * ci: revert "revert ci: remove redundant docs workflow (NVIDIA#725)" (NVIDIA#856) This reverts commit 36fa334. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Co-authored-by: Miyoung Choi <miyoungc@nvidia.com>
This reverts commit b18627f.
* fix(ci): post docs preview comment with explicit PR number The workflow_run context has no github.event.pull_request.number, so rossjrw/pr-preview-action's internal sticky comment silently skips posting. Disable its built-in comment and add an explicit marocchino/sticky-pull-request-comment step that passes the PR number from the artifact metadata. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * test: test * fix: remove test * ci: revert "revert ci: remove redundant docs workflow (NVIDIA#725)" (NVIDIA#856) This reverts commit 36fa334. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Co-authored-by: Miyoung Choi <miyoungc@nvidia.com>
Reverts #725
Summary by CodeRabbit