I think it depends. It is not always possible that is true.

But if it is a standalone feature I always suggest building a sub-part of that feature and put it behind a feature flag.

E.g. you want to build a new Analytics Feature

• Start with the button to the new feature
• Add the API routes
• Add one pane

Etc. And if everything is behind a feature flag for example just for team members this is easily possible to make smaller PRs.

I think it is not possible to have small prs for things like huge refactors.

For example you want to combine all common components of all pages in your next app from pages/* into _app then you need to touch all files within one PR and this will result in a huge one.

Sandro Volpicella

I think before using feature flags and shrink everything into smaller PRs a team should always try to focus on the business increment for the user and make that small as possible in the first place. Sure, this is a hard thing but from my perspective a „big“ feature comes always with „big“ testing efforts regardless of the PR sizes and makes it anyway hard to review

Thanks! If you're interested in the topic definitely read both mentioned articles :)

Sandro Volpicella Sure, I will 👌