That Was Annoying

Now imagine if testing wasn't as simple as just looking at a file... manually running automated tests can take as long as compiling a gasp enterprise Java project.

-- xkcd

From man git-bisect:

   Bisect run
       If you have a script that can tell if the current source code is good or bad, you can
       bisect by issuing the command:

           $ git bisect run my_script arguments

       Note that the script (my_script in the above example) should exit with code 0 if the
       current source code is good/old, and exit with a code between 1 and 127 (inclusive),
       except 125, if the current source code is bad/new.

Assignment

For science, let's see if we can redo what we just did, but automate the whole thing away.

Create a new script in scripts/ called bisect.sh with these contents:

if grep -q "SCANNING" "scripts/scan.sh"; then
    exit 1
else
    exit 0
fi

chmod its permissions to make it executable
Run git bisect start
Mark the current commit as bad with git bisect bad HEAD
Mark the first commit on main as good with git bisect good HASH
Automate the rest of the bisect with git bisect run ./scripts/bisect.sh
Did it find the same bad commit?
You can delete the bisect.sh script now, no need to commit it