Britton Leo Kerin <britton.kerin@xxxxxxxxx> writes: > +test_expect_success 'git bisect - start subcommand arguments before double-dash are completed as revs' ' > + ( > + cd git-bisect && > + test_completion "git bisect start " <<-\EOF > + HEAD Z > + final Z > + initial Z > + master Z > + EOF > + ) > +' When GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME is set to 'main' (can be seen as a failure in linux-gcc job in GitHub CI), this piece breaks the test, because 'master' would not appear there in the list. You could detect what the initial default branch name currently is and use that branch name to dynamically generate the above list during the test. I do not think it is worth it, and forcing the fixed name should be sufficient. Perhaps like this (not tested): diff --git a/t/t9902-completion.sh b/t/t9902-completion.sh index 698e278450..26f616fcfe 100755 --- a/t/t9902-completion.sh +++ b/t/t9902-completion.sh @@ -5,6 +5,8 @@ test_description='test bash completion' +GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME=master +export GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME . ./lib-bash.sh complete ()
