Hello, On Sat 16 Aug 2025 at 08:06pm +01, Ian Jackson wrote:
> Package: git-debpush > Version: 13.12 > > Watching the t2u logs I saw another job failed because the tag was > 404 where the whole repository was also 404, probably because the repo > permissions were misconfigured. This has happened several times now. > > I think git-debpush could detecct this, if we're prepared to give it > salsa-specific information. I think it is okay for the checks to make use of forge-specific information like this, so long as we abstract it properly. We'll want to be able to easily add Debian's next forge. > In particular, if the remote is > [email protected]:user/project > then we should check that > https://salsa.debian.org/user/project.git > is reachable via git without athentication. Or something. > > Empirically: > > git-ls-remote https://salsa.debian.org/dgit-team/dgit.git '' > # exit status 0, printing nothing > > git-ls-remote https://salsa.debian.org/dgit-team/no-such-repo.git '' > # prompts for a username > # same behaviour for a repo that I think exists privately Looking at a program of mine: we'll want to export GIT_TERMINAL_PROMPT=0 to avoid actually prompting, and possibly GIT_ASKPASS=/bin/true. -- Sean Whitton
signature.asc
Description: PGP signature
