fix(ci): explicitly request contents:write permission for app token#355
Conversation
Add permission-contents:write to the create-github-app-token step to ensure the generated token explicitly includes write access to contents (including releases). The installation already has contents:write, but explicitly scoping the token may resolve the 403 on release creation.
✅ Deploy Preview for devsydev canceled.
|
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
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 |
1 participant
Summary
contents: writeat the org level, but the generated token may not be getting the write scopepermission-contents: writetoactions/create-github-app-token@v3explicitly requests that the installation token be scoped with contents write accessHTTP 403: Resource not accessible by integrationerror on thecreate stable releasestep