From 21569fa96f86e06e60c6a9b238f50f0e8152c67c Mon Sep 17 00:00:00 2001 From: Stefan Haller Date: Sat, 31 Oct 2026 07:55:02 +0100 Subject: [PATCH] Add a test showing that a finished bisect labels the last commit "current" Once git has nothing left to test, the commit that the user marked last stays the current commit. The commits view labels it "<-- current", although it is marked good or bad now, and git doesn't want the user to test it any more. Co-Authored-By: Claude Opus 5.5 --- .../tests/bisect/select_first_bad_commit.go | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/pkg/integration/tests/bisect/select_first_bad_commit.go b/pkg/integration/tests/bisect/select_first_bad_commit.go index 16f86badc..2e83e1831 100644 --- a/pkg/integration/tests/bisect/select_first_bad_commit.go +++ b/pkg/integration/tests/bisect/select_first_bad_commit.go @@ -34,6 +34,16 @@ var SelectFirstBadCommit = NewIntegrationTest(NewIntegrationTestArgs{ t.ExpectPopup().Alert().Title(Equals("Bisect complete")).Content(MatchesRegexp("(?s)commit-08.*Do you want to reset")).Cancel() }). - SelectedLine(Contains("CI commit-08").Contains("<-- bad")) + TopLines( + Contains("CI commit-10"), + Contains("CI commit-09"), + Contains("CI commit-08").Contains("<-- bad").IsSelected(), + /* EXPECTED: + Contains("CI commit-07").Contains("<-- good"), + ACTUAL: */ + Contains("CI commit-07").Contains("<-- current"), + Contains("CI commit-06"), + Contains("CI commit-05").Contains("<-- good"), + ) }, })