From 2fb1cc17f0c57f3f482791390e6c81eb5f906bc9 Mon Sep 17 00:00:00 2001 From: Matt Hunter Date: Sun, 10 May 2026 03:08:00 -0400 Subject: precheck: Improve bisect detection After a bisect session begins and up until the first 'bad' and 'good' revisions are identified, BISECT_EXPECTED_REV is undefined, and the freshly started session goes undetected by git-precheck. Among a few potential alternatives, BISECT_START is a better signal, as it covers this gap and exists for the entire duration of a session - from 'git bisect start' to 'git bisect reset'. The file-based detection paradigm makes this choice more obvious. Signed-off-by: Matt Hunter --- git-precheck | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/git-precheck b/git-precheck index 0c6bc98..fa42eb3 100755 --- a/git-precheck +++ b/git-precheck @@ -81,7 +81,7 @@ check rebase-apply rebase/am check MERGE_HEAD merge check REVERT_HEAD revert check CHERRY_PICK_HEAD cherry-pick -check BISECT_EXPECTED_REV bisect +check BISECT_START bisect if [ -n "$opt_dirty" ] || [ -n "$opt_untracked" ]; then git_status="$(git status --porcelain 2>/dev/null)" -- cgit v1.2.3