From: Harald Nordgren Date: Tue, 09 Jun 2026 07:52:30 GMT Subject: Re: [PATCH v13 2/6] branch: let delete_branches warn instead of error on bulk refusal Message-ID: In-Reply-To: > This breaks t5404, t5514, and t5505, which contradicts with > "Existing callers are unaffected". > > What's going on? It is troubling that the breakage happens without > even getting merged with other topics in-flight, which means that > the environment you are developing in and testing on and the > environment that I apply patches on, integrate and test (something > based on Debian testing) are somehow behaving differently. > > "cd t && sh t5404-*.sh -i -v" ends like so: > > expecting success of 5404.7 'already deleted tracking branches ignored': > git branch -d -r origin/b3 && > git push origin :b3 >output 2>&1 && > ! grep "^error: " output > > error: the branch 'origin/b3' is not fully merged > hint: If you are sure you want to delete it, run 'git branch -D origin/b3' > hint: Disable this message with "git config set advice.forceDeleteBranch false" > not ok 7 - already deleted tracking branches ignored > # > # git branch -d -r origin/b3 && > # git push origin :b3 >output 2>&1 && > # ! grep "^error: " output > # > 1..7 > > but it may be possible that earlier steps are behaving differently > with the patches applied. I didn't dig further but I think the CI > in the recent past have been affected by the same breakage. Thanks for directing my attention to this. The GitHub CI has been broken for some time, maybe I should have told you about this earlier, but it coincided with a period where other open source projects I worked on also had mass CI failures, so I chalked it up to upstream issues (GitHub, Linux, etc). But it seems to have not gone away. All of my GitHub pull requests have broken tests (see e.g. which a quite minimal change: https://github.com/git/git/pull/2313). This makes it harder to detect actual issues. But of course it's not an excuse. Harald