-
it explains it in literally the first paragraph: https://github.com/tummychow/git-absorb?tab=readme-ov-file#g...
> The command essentially looks at the lines that were modified, finds a changeset modifying those lines, and amends that changeset to include your uncommitted changes.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
There seems to be an alternative implementation called git-autofixup: https://github.com/torbiak/git-autofixup
Has anyone compared the two?
-
Nice! I use git revise[^1] a lot which does a similar thing but without the fixup commit. I I’ll try using fzf to make it interactive though. Thanks!
[^1]: https://github.com/mystor/git-revise
-
git-test
Run automated tests against a range of Git commits and keep track of the results (by mhagger)
A revert two weeks after the fact will create a new and unique tree (untested) in any case. I don’t if you’re saying that the original commit or the revert might be untested.
In either case the brand new revert could break something. Who knows, it’s a new state.
> It doesn't happen often enough in my experience too convince me to give up a cleaner history, but it's a downside we should acknowledge.
There are tools for that.
https://github.com/mhagger/git-test
-
This looks a lot like git-fixup[1], which I have been using for a few years. I might try git-absorb since it looks quite interesting.
[1] https://github.com/keis/git-fixup
-
Lazygit has its own built-in approach to this problem which is much more strict than what git-absorb does (it explicitly asks for confirmation if there's any ambiguity). There's an extensive writeup about it here: https://github.com/jesseduffield/lazygit/blob/master/docs/de...
-