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
A Workflow Copilot. Tailored to You.
Our desktop app, with its intelligent copilot, streamlines coding by generating snippets, extracting code from screenshots, and accelerating problem-solving.
Read next
6 Essential Python Design Patterns for Scalable Software Architecture
Aarav Joshi -
AI Models Can Now Self-Improve Through Structured Multi-Agent Debates
Mike Young -
The Dark Side of Japan's Early 1990s Software Development - Young Engineers as Disposable Resources
Taka Saito -
Errors as a learning
DMS DB -
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: