This sounds too good to be true :) > Instead of manually finding commit SHAs for git commit --fixup, or running a manual interactive rebase, do this: > git add $FILES_YOU_FIXED > git absorb --and-rebase > git absorb will automatically identify which commits are safe to modify, and which staged changes belong to each of those commits. It will then write fixup! commits for each of those changes. Reproducible: Always
Maybe @dlan could help, since this is also a Rust Cargo package, like dev-vcs/stgit.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3588cf3ef186b48ed171944521ac36910c91f300 commit 3588cf3ef186b48ed171944521ac36910c91f300 Author: Yixun Lan <dlan@gentoo.org> AuthorDate: 2023-03-20 14:51:57 +0000 Commit: Yixun Lan <dlan@gentoo.org> CommitDate: 2023-03-20 14:58:20 +0000 dev-vcs/git-absorb: new package, add 0.6.9 Closes: https://bugs.gentoo.org/901495 Signed-off-by: Yixun Lan <dlan@gentoo.org> dev-vcs/git-absorb/Manifest | 68 +++++++++++++++++++ dev-vcs/git-absorb/git-absorb-0.6.9.ebuild | 101 +++++++++++++++++++++++++++++ dev-vcs/git-absorb/metadata.xml | 11 ++++ 3 files changed, 180 insertions(+)
U r hero @dlan!
