From: Harald Nordgren Date: Thu, 25 Jun 2026 07:53:22 GMT Subject: Re: [PATCH v2 2/2] push: suggest for a slash slip Message-ID: In-Reply-To: > Junio C Hamano writes: > > > "Harald Nordgren via GitGitGadget" writes: > > > >> diff --git a/t/t5529-push-errors.sh b/t/t5529-push-errors.sh > >> index 80b06a0cd2..cfb294305d 100755 > >> --- a/t/t5529-push-errors.sh > >> +++ b/t/t5529-push-errors.sh > >> @@ -54,6 +54,37 @@ test_expect_success 'detect empty remote with targeted refspec' ' > >> grep "fatal: bad repository ${SQ}${SQ}" stderr > >> ' > > t5529-push-errors.sh:59: error: bare grep outside pipeline (use test_grep) > > t5529-push-errors.sh:60: error: bare grep outside pipeline (use test_grep) > > t5529-push-errors.sh:62: error: bare grep outside pipeline (use test_grep) > > t5529-push-errors.sh:67: error: bare grep outside pipeline (use test_grep) > > t5529-push-errors.sh:72: error: bare grep outside pipeline (use test_grep) > > t5529-push-errors.sh:77: error: bare grep outside pipeline (use test_grep) > > t5529-push-errors.sh:84: error: bare grep outside pipeline (use test_grep) > > I've queued this squashable? fix on top of the branch before merging > the result to 'seen' for tonight's push-out. > > Thanks. Thank you! Is someone working on fixing the GitHub CI? I used to rely on it before, it would have caught this, and now I'm relying on "if less than five GitHub CI tests are failing (with the 4GB warning) and tests are passing locally, then I can submit" which is admittedly not a good heuristic. Harald