ci: allow ready-for-review workflow to edit labels#810
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughExplicit ChangesReady-for-Review Workflow Permission Fix
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
|
@coderabbitai review |
✅ Action performedReview finished.
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## dev #810 +/- ##
==========================================
- Coverage 72.97% 72.93% -0.04%
==========================================
Files 323 323
Lines 71989 71989
==========================================
- Hits 52534 52507 -27
- Misses 19455 19482 +27
|
|
This PR has merge conflicts with the base branch. Please rebase or merge the base branch into your branch to resolve them. |
Ready-for-review label permissions
Summary
contents: read.issues: writeonly to theevaluatejob that mutates PR labels.label-removal cleanup paths.
Fixes #809.
Motivation
The ready-for-review workflow currently reaches:
and then fails with:
GitHub PR labels are issue labels, so the workflow needs
issues: writewhencalling
gh pr edit --add-labelorgh pr edit --remove-label.Validation
python3assertion check confirmed the workflow contains scopedissues: writepermissions and non-fatal add-label handling.git diff --check upstream/dev..HEADcode-review dashpay/rust-dashcore upstream/dev fork/fix-ready-for-review-permissionsSummary by CodeRabbit