Files
git/builtin
Jonas Rebmann 6f2387cfdf bisect: use selected alternate terms in status output
Alternate bisect terms are helpful when the terms "good" and "bad" are
confusing such as when bisecting for the resolution of an issue (the
first good commit) rather than the introduction of a regression. If
alternate terms are chosen, the terms "good" and "bad" should not be
used in git's output to avoid confusion.

An old/new bisect should end with
$ git bisect old
[sha] is the first new commit

not with
$ git bisect old
[sha] is the first bad commit

Using hardcoded good/bad vocabulary can give confusion about what action
is required:

  status: waiting for bad commit, 1 good commit known
  $ git bisect bad
  error: Invalid command: you're currently in a new/old bisect
  fatal: unknown command: 'bad'

To avoid confusion, use alternate terms consistently across the bisect
output.

Signed-off-by: Jonas Rebmann <kernel@schlaraffenlan.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2026-03-20 21:58:58 -07:00
..
2026-02-20 08:13:58 -08:00
2026-03-12 14:09:07 -07:00
2025-07-23 08:15:18 -07:00
2025-09-29 11:40:35 -07:00
2025-07-23 08:15:18 -07:00
2026-02-23 13:23:41 -08:00
2025-07-23 08:15:18 -07:00
2025-07-23 08:15:18 -07:00
2025-07-01 14:46:38 -07:00
2026-03-09 14:36:55 -07:00
2025-08-22 13:13:20 -07:00
2026-03-09 14:36:55 -07:00
2026-03-12 14:09:07 -07:00
2026-02-19 13:24:57 -08:00
2025-07-16 22:16:15 -07:00
2025-12-25 08:29:27 +09:00
2025-08-21 13:47:00 -07:00
2026-03-12 14:09:07 -07:00
2026-03-10 14:23:18 -07:00
2025-10-02 12:26:12 -07:00
2025-07-23 08:15:18 -07:00
2026-02-20 08:13:58 -08:00
2025-07-23 08:15:18 -07:00
2025-09-16 11:37:06 -07:00
2025-08-21 13:46:59 -07:00