Skip to content

docs: warn about ray.sub shared-venv drift and pre-sync fix #5406

docs: warn about ray.sub shared-venv drift and pre-sync fix

docs: warn about ray.sub shared-venv drift and pre-sync fix #5406

Workflow file for this run

name: Claude Code Review
on:
issue_comment:
types: [created]
permissions:
contents: read
pull-requests: write
issues: write
id-token: write
jobs:
claude-review:
if: github.event.issue.pull_request != null && contains(fromJson('["OWNER", "MEMBER", "COLLABORATOR"]'), github.event.comment.author_association)
uses: NVIDIA-NeMo/FW-CI-templates/.github/workflows/_claude_review.yml@v1.7.0
with:
model: ${{ vars.CLAUDE_MODEL }}
prompt: |
Mandatory workflow — never skip or reorder:
1. Read the PR diff first.
2. Based on the changed files and areas, identify relevant skills from skills/<name>/SKILL.md.
Common skill names: linting-and-formatting, testing, cicd, build-and-dependency,
contributing, copyright, docs, error-handling, config-conventions, launch-nemo-rl.
3. Read the SKILL.md files for all relevant areas using the Read tool.
4. Only then perform the review using the skill context.
You are doing a light code review. Keep it concise and actionable.
Focus ONLY on:
- Critical bugs or logic errors
- Typos in code, comments, or strings
- Missing or insufficient test coverage for changed code
- Outdated or inaccurate documentation affected by the changes
Do NOT comment on:
- Style preferences or formatting
- Minor naming suggestions
- Architectural opinions or refactoring ideas
- Performance unless there is a clear, measurable issue
Provide feedback using inline comments for specific code suggestions.
Use top-level comments for general observations.
It's perfectly acceptable to not have anything to comment on.
If you do not have anything to comment on, post "LGTM".
secrets:
NVIDIA_INFERENCE_URL: ${{ secrets.NVIDIA_INFERENCE_URL }}
NVIDIA_INFERENCE_KEY: ${{ secrets.NVIDIA_INFERENCE_KEY }}