Network calls are cheap, and it is already doing them to salsa.debian.org. It is way more expensive to have humans - potentially many of them - to debug what is going on when their work got halted by interactions with a broken package in the Debian archive. Doing cleanup type of work is also very demotivating for volunteers, and utilizing CI helps by preventing problems and the need for cleanup to arise in the first place. If Salsa CI exists for a package I think we should make it as easy as possible for people to use it.
If you don't want git-debpush to have this new check along the other checks it has, what do you think would be a better place to do this CI gatekeeping in the tag2upload pipeline? To me using git-debpush seems quite ideal for this, especially as it already has a list of various checks.
