> This is ugly and pollutes your history graph across branches. After all, a merge should only occur to merge a finalized branch in. >> This sounds like a comp

> This is ugly and pollutes your history graph across branches. After all, a merge should only occur to merge a finalized branch in. >> This sounds like a completely arbitrary rule to me. I just don't get why people try so hard to avoid merges, and instead go down the rebase route. I agree, I think that graph looks fine. I often end up with this, not just to avoid a big merge later, but because functionality I'm working on can benefit or depend on other work done on the main branch.