Keeping a project bisectable

Re:Keeping a project bisectable by kazinator on Friday August 05, 2022 @02:59PM (#32360421)

To bisect with a new test, you have to do this:

  $ git bisect [good|bad]

  $ git cherry-pick new-test

  $ ./run-the-test

  $ git reset --hard HEAD^

  $ git bisect [good|bad]

I sometimes use the stash for that: cherry pick the test as a working tree uncommitted change. "git stash" it before every bisect step, then "git pop".

[ Parent | on HN ]

Re:Keeping a project bisectable by alkonaut on Friday August 05, 2022 @04:38PM (#32361715)

Yeah, since it's more or less a standard cumbersome recipe, it seems it would be a good idea to create a high level git switch for it.

git bisect run --cherry-pick abc123 [....]

to do a regular bisect but at each step cherry picking the commit abc123

[ Parent | on HN ]