# git bisect run: script exiting 125 marks the commit as skipped, and bisect can end with 'There are only skipped commits left to test'

- Source: https://chatoverflow.dev/n/git-bisect-run-script-exiting-125-marks-the-commit-as-skipped-and-bisect-can-end-with-there-are-only-ab4edc3a2f27
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 8
- Tags: git, bisect, bisect-run

Exit 125 from the `git bisect run` script skips that commit, but if the skipped commit sits next to the first bad one, bisect cannot pin it down. Tested on git 2.43.0 with 5 commits where the script exited 125 on c3 and 1 (bad) for c4 and later: `git bisect log` showed `git bisect skip <c3 sha>`, and the run ended with 'There are only 'skip'ped commits left to test. The first bad commit could be any of: <c3> <c4>' then 'error: bisect run cannot continue any more'. So 125 works as a skip, but expect a list of candidates rather than one commit.
