Move coverage helper scripts into action directories#25
Conversation
Reviewer's GuideScripts for coverage generation and ratcheting have been moved into their respective action directories, and the action YAML files have been updated to reference the new script locations by leveraging the github.action_path and relative paths in run steps. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
|
Warning Rate limit exceeded@leynos has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 8 minutes and 15 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📒 Files selected for processing (3)
Summary by CodeRabbit
Summary by CodeRabbit
Summary by CodeRabbit
Summary by CodeRabbit
WalkthroughThe changes update GitHub Actions workflow files to use fully qualified script paths by leveraging the Changes
Possibly related PRs
Poem
✨ Finishing Touches
🧪 Generate Unit Tests
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Actionable comments posted: 3
♻️ Duplicate comments (1)
.github/actions/generate-coverage/action.yml (1)
73-74: Sameuv-before-install issue as above – see earlier comment.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
📒 Files selected for processing (2)
.github/actions/generate-coverage/action.yml(4 hunks).github/actions/ratchet-coverage/action.yml(2 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
`.github/actions/*/{action.yml,README.md,CHANGELOG.md,src/,tests/}`: Each action...
.github/actions/*/{action.yml,README.md,CHANGELOG.md,src/,tests/}: Each action must have its own directory under .github/actions/, containing action.yml, README.md, src/, tests/, and CHANGELOG.md
📄 Source: CodeRabbit Inference Engine (AGENTS.md)
List of files the instruction was applied to:
.github/actions/ratchet-coverage/action.yml.github/actions/generate-coverage/action.yml
`.github/actions/*/action.yml`: Fill in action.yml with every input and output; ...
.github/actions/*/action.yml: Fill in action.yml with every input and output; mark required ones clearly
For composite actions and path context, use "${{ github.action_path }}" when referencing sibling scripts for portability
📄 Source: CodeRabbit Inference Engine (AGENTS.md)
List of files the instruction was applied to:
.github/actions/ratchet-coverage/action.yml.github/actions/generate-coverage/action.yml
🔇 Additional comments (5)
.github/actions/ratchet-coverage/action.yml (1)
46-47: Path change looks good – resolves correctly under${{ github.action_path }}
No further issues spotted..github/actions/generate-coverage/action.yml (4)
82-90: Cross-action relative path is valid
Using"${{ github.action_path }}/../ratchet-coverage/scripts/ratchet_coverage.py"keeps the dependency internal to the repository while remaining portable. Looks good.
121-122: Path normalisation OK
The script location update matches the new directory layout; no issues detected.
127-128: Path normalisation OK
134-135: Path normalisation OK
There was a problem hiding this comment.
Actionable comments posted: 1
🔭 Outside diff range comments (1)
.github/actions/ratchet-coverage/action.yml (1)
3-7: Add an explicittype: stringforbaseline-fileto stay consistent with other inputs
YAML-level validation is clearer when every input declares its type.baseline-file: description: Path to store the coverage baseline required: false + type: string default: .coverage-baseline
♻️ Duplicate comments (3)
.github/actions/ratchet-coverage/action.yml (2)
19-21:uvbootstrap now happens before first use – good catch
Moving theastral-sh/setup-uv@v5step to the top eliminates the cold-runner failure that was flagged earlier.
52-53: Baseline file is now passed explicitly – previous gap resolved
Forwarding--baseline-filemakes the action self-contained and removes hidden coupling inside the Python script..github/actions/generate-coverage/action.yml (1)
48-49: Earlyuvsetup prevents the previously reported failure
Placingsetup-uvbefore anyuv runinvocation resolves the runner bootstrapping issue.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
📒 Files selected for processing (2)
.github/actions/generate-coverage/action.yml(4 hunks).github/actions/ratchet-coverage/action.yml(3 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
`.github/actions/*/{action.yml,README.md,CHANGELOG.md,src/,tests/}`: Each action...
.github/actions/*/{action.yml,README.md,CHANGELOG.md,src/,tests/}: Each action must have its own directory under .github/actions/, containing action.yml, README.md, src/, tests/, and CHANGELOG.md
📄 Source: CodeRabbit Inference Engine (AGENTS.md)
List of files the instruction was applied to:
.github/actions/ratchet-coverage/action.yml.github/actions/generate-coverage/action.yml
`.github/actions/*/action.yml`: Fill in action.yml with every input and output; ...
.github/actions/*/action.yml: Fill in action.yml with every input and output; mark required ones clearly
For composite actions and path context, use "${{ github.action_path }}" when referencing sibling scripts for portability
📄 Source: CodeRabbit Inference Engine (AGENTS.md)
List of files the instruction was applied to:
.github/actions/ratchet-coverage/action.yml.github/actions/generate-coverage/action.yml
There was a problem hiding this comment.
Actionable comments posted: 2
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
📒 Files selected for processing (1)
.github/actions/ratchet-coverage/action.yml(4 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
`.github/actions/*/{action.yml,README.md,CHANGELOG.md,src/,tests/}`: Each action...
.github/actions/*/{action.yml,README.md,CHANGELOG.md,src/,tests/}: Each action must have its own directory under .github/actions/, containing action.yml, README.md, src/, tests/, and CHANGELOG.md
📄 Source: CodeRabbit Inference Engine (AGENTS.md)
List of files the instruction was applied to:
.github/actions/ratchet-coverage/action.yml
`.github/actions/*/action.yml`: Fill in action.yml with every input and output; ...
.github/actions/*/action.yml: Fill in action.yml with every input and output; mark required ones clearly
For composite actions and path context, use "${{ github.action_path }}" when referencing sibling scripts for portability
📄 Source: CodeRabbit Inference Engine (AGENTS.md)
List of files the instruction was applied to:
.github/actions/ratchet-coverage/action.yml
🔇 Additional comments (3)
.github/actions/ratchet-coverage/action.yml (3)
7-7: Declare input type – nice additionExplicitly setting
type: stringmakes the composite action schema clearer and prevents metadata-parsing edge-cases.
39-39: Absolute script path improves portability – looks goodMigrating to
${{ github.action_path }}avoids path-resolution issues when the working directory changes.
52-54: Explicit--baseline-fileforwarding – LGTMPassing the baseline path explicitly removes magic defaults and aligns with previous review feedback.
There was a problem hiding this comment.
Actionable comments posted: 2
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
📒 Files selected for processing (6)
.github/actions/generate-coverage/action.yml(4 hunks).github/actions/ratchet-coverage/CHANGELOG.md(0 hunks).github/actions/ratchet-coverage/README.md(0 hunks).github/actions/ratchet-coverage/action.yml(0 hunks)CODEOWNERS(0 hunks)README.md(0 hunks)
💤 Files with no reviewable changes (5)
- CODEOWNERS
- README.md
- .github/actions/ratchet-coverage/CHANGELOG.md
- .github/actions/ratchet-coverage/README.md
- .github/actions/ratchet-coverage/action.yml
🧰 Additional context used
📓 Path-based instructions (2)
`.github/actions/*/{action.yml,README.md,CHANGELOG.md,src/,tests/}`: Each action...
.github/actions/*/{action.yml,README.md,CHANGELOG.md,src/,tests/}: Each action must have its own directory under .github/actions/, containing action.yml, README.md, src/, tests/, and CHANGELOG.md
📄 Source: CodeRabbit Inference Engine (AGENTS.md)
List of files the instruction was applied to:
.github/actions/generate-coverage/action.yml
`.github/actions/*/action.yml`: Fill in action.yml with every input and output; ...
.github/actions/*/action.yml: Fill in action.yml with every input and output; mark required ones clearly
For composite actions and path context, use "${{ github.action_path }}" when referencing sibling scripts for portability
📄 Source: CodeRabbit Inference Engine (AGENTS.md)
List of files the instruction was applied to:
.github/actions/generate-coverage/action.yml
🔇 Additional comments (5)
.github/actions/generate-coverage/action.yml (5)
48-49:uvnow installed before first usage – nice catch.Placing
astral-sh/setup-uv@v5at the very top eliminates the “uv: command not found” failure reported earlier.
No further issues spotted here.
75-76: Script path is now self-contained – good clean-up.Switching to
${{ github.action_path }}/scripts/run_rust.pyremoves the fragile../traversal and makes packaging safer.
120-121: Path update looks correct.
run_python.pynow resolves relative to the action – portable and Marketplace-safe.
126-127: Merge script path updated – LGTM.
No functional change beyond improved portability.
133-134: Output-setting script path updated – LGTM.
Everything aligns with the new directory layout.
Summary
Testing
git log -1 --stathttps://chatgpt.com/codex/tasks/task_e_686a8823e6bc832281c92cd1b6899bc6
Summary by Sourcery
Move coverage helper scripts into their respective action directories and update GitHub Actions workflows to point to the new script locations.
Enhancements:
CI: