Re:The lazy Git UI you didn't know you need
by skydhash on Monday November 10, 2025 @05:47PM
(#45882000)
Git 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.
[ Parent
| on HN ]
Re:The lazy Git UI you didn't know you need
by gpderetta on Tuesday November 11, 2025 @05:59AM
(#45886037)
Yes, 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.
Re:The lazy Git UI you didn't know you need
by 1718627440 on Tuesday November 11, 2025 @07:06AM
(#45886384)
> 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.