3 ms·
That's why when you use a "history is sacred" approach, you typically have several branches and use merge commits, not rebase. When you look at the master bran
by GuB-42 4y ago
That's why when you use a "history is sacred" approach, you typically have several branches and use merge commits, not rebase.
When you look at the master branches you will mostly see merge commits, all the mess will be on the side, for example in feature branches. Merge commits can be clean, and when you are blaming, you will see the merge commit, not the dozen of typo commits. If you do "git log --first-parent" you will not even see the messy commits, but they will be there if you need them.