Blueprint, plus milestone PRs. To the extent it makes sense to split something into separate commits, I think having it in separate PRs is also fine. It has the con of potentially merging something prior to being fully realized, which might be dropped. But. it’s also a lot easier to manage if the codebase is changing and its hard to maintain. (eg: standard agile arguments) Or, separate commits in a PR, and squash merge. After the merge happens I, personally. almost never care about picking apart the PR. (You mention you did, during bisect, it hasn’t been something I’ve needed)