Skip to main content

One post tagged with "Code Review"

Best practices for giving and receiving better feedback on code.

View All Tags

How to Keep PRs Small When Features Depend on Each Other

· 3 min read
Darren Lin
Blogger

We all know that huge Pull Requests are a pain. Most teams suggest keeping PRs between 25 and 200 lines because they are easier to review and less likely to introduce bugs. But what should you do when you are working on a new feature that depends on code you just wrote in another branch?

Instead of cramming everything into one giant 1,000 line PR, you can use Stacked PRs to keep your git workflow smooth and clean.