3 ms·
The task that absorb speeds up is finding the commit where each hunk was last changed. The actual committing and rebaseing is still basically the same.
by 1718627440 1y ago
The task that absorb speeds up is finding the commit where each hunk was last changed. The actual committing and rebaseing is still basically the same.
- skydhash 1y agoGit blame using `M-x vc-annotate` with Emacs. But If I have a clean PR that usually means one to three commits (If it's not a big refactoring). So the whole point become moot. In magit, if you create a fixup or a squash commit, it will present you with the log to select the target.
- gpderetta 1y agoYes, or magit-blame, but if you still have multiple commits in your history that you are working on, and you need to break up the current changes in a bunch of instant fixups, figuring out which one is the right one can be a bit time consuming. I'm not convinced that automatically amending to the last commit that touched that line is safe, but I'm willing to try git-absorb.
- 1718627440 1y ago> I'm not convinced that automatically amending to the last commit that touched that line is safe, but I'm willing to try git-absorb. It is not, but git absorb only produces fixup commits, you can still change what they change in the autosquash step.