Here's better rationale for this kind of approach: it requires a lot less rebasing and merging: 1) If you branch a lot, keeping up with upstream changes can be

Here's better rationale for this kind of approach: it requires a lot less rebasing and merging: 1) If you branch a lot, keeping up with upstream changes can be tedious: you have to rebase each branch separately just to keep up. With this method, to keep up, you rebase just once, on your one branch. 2) If you branch a lot, merging each branch can cascade into a bunch of rebasing. As you build your feature, you might clean up unrelated code. Your "implement feature" commits could be interspersed with "fix unrelated code" commits. If you're creating a branch for each cleanup commit, as you submit them for review earlier than your feature, you have to rebase all your branches one by one. With this method, you rebase just once.