Repository navigation
ci(fast-path): never save caches; per-run concurrency - #44
Conversation
The fast path builds unreviewed refs, so it must not save into caches that normal CI restores. The workflow concurrency group gets github.run_id so a later dispatch cannot cancel a run that is waiting for approval. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 32 minutes. View limit details
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. |
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
[Medium impact] This PR appears safe to merge.
|
Hardens the approval-gated fast path (
.github/workflows/fast-path.yml) from the earlier fast-path PR. Normal CI is unchanged, and Khaliq still approves thefast-pathenvironment before anything runs on Blacksmith.Cache poisoning: the fast path builds unreviewed refs, so it must never save into a cache that normal CI or release workflows restore. Removes
cache: npmfrom all threeactions/setup-nodesteps.Concurrency: the workflow-level group now includes
github.run_id. With a group keyed only byref, a later dispatch could cancel a run that was still waiting for approval.No workflow test harness exists in this repo, so no property test was added.
🤖 Generated with Claude Code
Open in [code]smith · Need help on this PR? Tag
@codesmith-botwith what you need.