4 ms·
No, the point is that you don't have to mention the hash at all, it's automatically deduced by diff context.
by jordigh 4y ago
No, the point is that you don't have to mention the hash at all, it's automatically deduced by diff context.
- raimue 4y agoThere is git-fixup, which provides the 'git fixup' command that makes suggestions to which commit the currently staged changes should be added. https://github.com/keis/git-fixup https://github.com/keis/git-fixup git-fixup will add fixup! commits, so it still needs the mentioned 'git rebase -i --autosquash' afterwards. Usually you do not even need to give it a specific commit if your branch is set to track an upstream branch.
- jordigh 4y agoStill not quite the same, because absorb splits up your working directory changes into all relevant commits, as deduced by diff context.
- hakre 4y agoStaged or unstaged? Sounds interesting, will give it a try. Thanks for the details.
- hakre 4y agoDipped into it. Staged changes, excluding renames. So git-fixup and git-absorb will now happily live together for the moment on my box. Made a good first impression, thanks again for the reference.