fix: scope peribolos concurrency per ref#560
Conversation
📝 WalkthroughWalkthroughModified the ChangesWorkflow Concurrency Update
Estimated code review effort: 1 (Trivial) | ~3 minutes Related Issues: None specified Related PRs: None specified Suggested Labels: ci, github-actions Suggested Reviewers: None specified Poem 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
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. Comment |
acf7110 to
b88f637
Compare
b88f637 to
96d1253
Compare
96d1253 to
49b4d6c
Compare
49b4d6c to
df99f2e
Compare
df99f2e to
9722a3c
Compare
The default GitHub Actions concurrency behavior cancels any pending run when a new one enters the same group, regardless of `cancel-in-progress: false`. This meant the ofep archival push run got evicted by later PR verify runs. Scope the group by ref so PR runs don't queue against the apply on main, and switch to `cancel-in-progress: true` so the newest apply wins (peribolos is idempotent against current config). Signed-off-by: Todd Baert <[email protected]>
9722a3c to
bb5c7e0
Compare
Small addendum to #555, so that we don't share concurrency across ALL runs (just per branch).