Remove GitHub token permissions from the CI checker#292
Conversation
They're no needed because of using the App Token.
|
Warning Rate limit exceeded@5ouma has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 20 minutes and 42 seconds before requesting another review. ⌛ 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. 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR/Issue comments)Type Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Pull Request Overview
This PR removes GitHub token permissions from the CI checker workflow, specifically removing contents: write and pull-requests: write permissions from the merge-pr job.
- Removes unnecessary GitHub token permissions from the merge-pr job
- Simplifies the workflow configuration by relying on App Token authentication instead
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
|
@coderabbitai approve |
✅ Actions performedComments resolved and changes approved. |
✅ Actions performedComments resolved and changes approved. |
close #
✏️ Description
They're not needed because of using the App Token.