Problem
Currently, extremely large pull requests (PRs) are challenging to review due to their size, making the code review process slower, less effective, and error-prone.
Proposal
Implement a batching mechanism for handling big PRs. This may include:
- Automatically splitting large PRs into manageable batches for review.
- Providing tools/guidelines for contributors to break down big changes into multiple smaller PRs.
- Improving documentation to encourage smaller, incremental submissions.
Expected Benefits
- Easier, more thorough reviews.
- Reduced cognitive load for reviewers.
- Faster, more reliable integration of changes.
Additional Context
- Investigate standard practices from popular repositories.
- Consider edge cases, such as binary files or large data updates.
If batching technically cannot be done automatically, document best practices and workflows for contributors.
Problem
Currently, extremely large pull requests (PRs) are challenging to review due to their size, making the code review process slower, less effective, and error-prone.
Proposal
Implement a batching mechanism for handling big PRs. This may include:
Expected Benefits
Additional Context
If batching technically cannot be done automatically, document best practices and workflows for contributors.