[daragh]

Create commits using `add -p` up to the point that the current state of the work tree is fully committed. (You can `reset HEAD^` if you need to add some stuff that you do not want to become part of your branch's history, at least not in its current form.) Then test using run-command-on-git-revisions[1] on the new commits.

This lets you create multiple commits at the same time and run tests on all of them. You could argue that committing and resetting is effectively the same thing as stashing and popping, but I think the benefits of being able to iterate over a list of commits and test each one is worth creating additional commits that you will probably reset shortly after testing.

This is also what you should do after a rebase to test all affected commits as they have not neccesarily existed in a testable state in the work tree.

[1] https://github.com/garybernhardt/dotfiles/blob/master/bin/ru...