-
-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feature(ci): limit pull request size to 500 #743
Conversation
Warning Rate Limit Exceeded@Idrinth has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 8 minutes and 7 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. WalkthroughThis collective enhancement introduces a workflow to maintain the efficiency of code reviews by limiting the size of pull requests to 500 lines, excluding specified files. It utilises an automated check to enforce this constraint, thereby streamlining the review process and ensuring code quality. Changes
Assessment against linked issues
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
Review Status
Configuration used: .coderabbit.yaml
Files selected for processing (1)
- .github/workflows/global.pull-request-size.yml (1 hunks)
Additional comments not posted (8)
.github/workflows/global.pull-request-size.yml (8)
1-1
: Name of workflow is appropriate and clear.
3-5
: Triggering on pull requests to master branch is logical for the intended purpose.
6-7
: Usage of environment variable for Node version provides flexibility.
10-10
: Choice ofubuntu-latest
ensures up-to-date environment.
12-12
: Use ofactions/checkout@v4
is standard practice.
13-24
: Configuration for Node.js setup is comprehensive, including caching.
25-25
: Global installation ofcheck-pr-length
is necessary for execution.
26-26
: Commandcheck-pr-length
correctly configured but lacks clarity on exclusion rationale.Consider adding a comment explaining the rationale behind excluding
package-lock.json
files from the PR length check. This will aid future maintainers in understanding the decision.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
Review Status
Configuration used: .coderabbit.yaml
Files selected for processing (1)
- .github/workflows/global.pull-request-size.yml (1 hunks)
Files skipped from review as they are similar to previous changes (1)
- .github/workflows/global.pull-request-size.yml
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
Review Status
Configuration used: .coderabbit.yaml
Files selected for processing (1)
- .github/workflows/global.pull-request-size.yml (1 hunks)
Files skipped from review as they are similar to previous changes (1)
- .github/workflows/global.pull-request-size.yml
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
Review Status
Configuration used: .coderabbit.yaml
Files selected for processing (1)
- .github/workflows/global.pull-request-size.yml (1 hunks)
Files skipped from review as they are similar to previous changes (1)
- .github/workflows/global.pull-request-size.yml
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
Review Status
Configuration used: .coderabbit.yaml
Files selected for processing (1)
- .github/workflows/global.pull-request-size.yml (1 hunks)
Files skipped from review as they are similar to previous changes (1)
- .github/workflows/global.pull-request-size.yml
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
Review Status
Configuration used: .coderabbit.yaml
Files selected for processing (1)
- .github/workflows/global.pull-request-size.yml (1 hunks)
Files skipped from review as they are similar to previous changes (1)
- .github/workflows/global.pull-request-size.yml
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
Review Status
Configuration used: .coderabbit.yaml
Files selected for processing (1)
- .github/workflows/global.pull-request-size.yml (1 hunks)
Files skipped from review as they are similar to previous changes (1)
- .github/workflows/global.pull-request-size.yml
Quality Gate passedIssues Measures |
The Pull Request is ready
Overview
Tools