When you work on large bodies of work, stacked PRs don't work...but you can't always split it up. What do you do with large PRs?
For further actions, you may consider blocking this person and/or reporting abuse
Read next
Integrating Java and Python for Successful Machine Learning Implementation: A Case Study
MyExamCloud -
Perl Weekly #667 - Call for papers and sponsors for LPW 2024
Gabor Szabo -
Common Mathematical Functions
Paul Ngugi -
I launched my real-time AI-powered meeting & interview copilot
Thomas Bradley -
Top comments (1)
PR size is secondary for me when considering how I'm packaging my code.
Ideally - my PRs are small enough to be easily consumable by reviewers, but the PR has to be able to land in the codebase and not block other collaborators on a given project.
When I do have a large PR, what I do to make it easier for my reviewers: