git bisect works by counting the number of commits between good and bad and checking for a change in the middle. Unfortunately, this will not work for the repo, because one project (for example, a wireframe) can have many changes at an early stage, and another project (for example, a kernel) can have a bunch of later changes, so "repo forall -c" git bisect ... "" maybe one project is tested in a state much older than another.
My question is whether there is a way to get git-bisect to choose its commit depending on the commit date, so when this is done in projects, we will most likely remain in a state that compiles cleanly.
source share