2 ms·
I don't consider a git UI to be complete unless it has interactive rebase support (ie, the ability to squash commits together so the history looks like 'impleme
by nailer 7y ago
I don't consider a git UI to be complete unless it has interactive rebase support (ie, the ability to squash commits together so the history looks like 'implement X', rather than 'implement X, 'fix X', 'minor typo on X', 'add additional unit test for X').
Command line is great if you prefer it, but Fork, SourceTree and Tower all have interactive rebase support. Here's me using Fork:
https://twitter.com/mikemaccana/status/1237708418124742656?s=20 https://twitter.com/mikemaccana/status/1237708418124742656?s...