fix(actions): add pull request write permission for ping spam workflow#473
fix(actions): add pull request write permission for ping spam workflow#473Nightkilller wants to merge 1 commit into
Conversation
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
👋 Thanks for opening a PR, @Nightkilller!Your PR has entered the 🚦 PR Review Pipeline.
What happens next
A pipeline status comment will appear below and update automatically as your PR progresses. While you wait
This comment is posted only once. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
WalkthroughThe detect-ping-spam workflow permissions are updated to grant ChangesWorkflow Permissions Update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 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 |
Summary
This PR fixes the detect-ping-spam workflow failing with:
HttpError: Resource not accessible by integration (403)
Root Cause
The workflow posts comments and applies labels on pull requests using the GitHub Issues API. However, the workflow only requested:
yaml permissions: issues: write contents: read
When operating on pull requests, GitHub requires the pull-requests: write permission.
Changes
Added the missing permission:
yaml permissions: issues: write pull-requests: write contents: read
Validation
Summary by CodeRabbit