"Nude F. Ninja" <nudefninja@xxxxxxxxx> writes:
> What did you do before the bug happened? (Steps to reproduce your issue)
> I ran git stash push, which created the stash entry "On main: dark
> mode". Then I committed changes before noticing an oversight with the
> previous commit. I wrote the fix and ran git commit --fixup :/dark
It is natural that there are multiple commits that match the pattern
you give in your repository.
One trick I learned that is effective is to explicitly state where
to start searches, e.g. "--fixup 'HEAD^{/dark mode}'", which would
be very much in line to what --fixup wants to do. The commit to be
fixed up in a later rebase session by definition must be an ancestor
of the current HEAD.
