Is there an ergonomic way to start a rebase after a `git bisect`?

Viewed 36

When doing exploratory works, especially GUI, I often create many commits before merging them into master (so I can safely rebase them). I often find bugs in those and use git bisect to identify the root cause. Since bisect knows on what branch I am currently, is there a way to create a commit/amend the last one, then immediately start a rebase of the branch I was on.

Currently, I do the needed modifications, stash them, copy the hash of the faulty commit, git bisect reset immediately followed by a git rebase --interactive $hash~, mark the commit for edit, git stash pop && git add -u && git rebase --continue. It works, but is there a more ergonomic way to do the same. Something like an hypothetical git bisect rebase --amend?

0 Answers
Related