Skip to content

ci: grant pull-requests write for the release-notes PR step - #23

Merged
moui72 merged 1 commit into
mainfrom
ci/stable-release-pr-permission
Jul 24, 2026
Merged

ci: grant pull-requests write for the release-notes PR step#23
moui72 merged 1 commit into
mainfrom
ci/stable-release-pr-permission

Conversation

@moui72

@moui72 moui72 commented Jul 24, 2026

Copy link
Copy Markdown
Owner

The v1.2.0 stable cut published successfully, but the workflow's final step failed with Resource not accessible by integrationgh pr create requires pull-requests: write, which ardd-badge.yml grants for the identical branch+PR idiom but the port in #21 missed. One-line permissions addition. (The orphaned v1.2.0 notes PR was opened manually as #22.)

🤖 Generated with Claude Code

https://claude.ai/code/session_01DPyUE4w2CWGbtyafYfhhxw

The v1.2.0 cut published fine but its final step died on
'Resource not accessible by integration' — gh pr create needs
pull-requests: write, which ardd-badge.yml grants for the same idiom
but the port to stable-release.yml missed.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DPyUE4w2CWGbtyafYfhhxw
@coderabbitai

coderabbitai Bot commented Jul 24, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@moui72, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 16 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 441d4aec-079e-42e7-a3e0-7af06086f12b

📥 Commits

Reviewing files that changed from the base of the PR and between 20d8960 and 8b71a39.

📒 Files selected for processing (1)
  • .github/workflows/stable-release.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch ci/stable-release-pr-permission

Comment @coderabbitai help to get the list of available commands.

@moui72
moui72 merged commit 6b39c3a into main Jul 24, 2026
47 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant