Open gigatexal opened 4 hours ago
i'm going to need more than that to reproduce the issue. what was the exact state of the repo in each case? (or are you saying you saw the fixup commit in the git log output before running git rebase? that's kind of the whole point. the rebase command is what squashes away the fixups)
Firstly, thank you for this free tool. It has sent me into a git fixup, git rebase rabbit hole and has expanded my knowledge of a git a bit more.
I was also won over by the first part of the elevator pitch:
https://github.com/tummychow/git-absorb?tab=readme-ov-file#elevator-pitch
I created a silly git repo, added a text file, committed it, then in another edit added another line, ran git absorb --and-rebase and it all worked as expected. There were no fixup! commits in the log.
BUT
Doing the above left the file in the right state of course but left the fixup! init commit in the log :-/ where I expected them to be equivalent i.e the fixup! init commit to be squashed.
I might be doing something wrong here so apologies if this is user error.
Running on git v 2.46.2 on M3 MacBook Pro on MacOS 15