On Tue, 2024-06-25 at 11:00 +0100, Ian Jackson wrote:
> Simon Richter writes ("Re: Summary of the current state of the tag2upload
> discussion"):
> > You can only call it "forgetting" to do a git push if you introduce a
> > policy that contributions to git-maintained packages have to be made
> > through git.
>
> In fact, tag2upload avoids this *even for NMUs made outside git* !
[...]
> But, with wide tag2upload adoption, things are even better:
>
> If everyone is using tag2upload[1], we simply avoid the problem,
> by avoiding the mistake. This is because git-debpush's default
> behaviour is to push your *branch* as well as just the *tag*.
>
> So the original mistake, of forgetting to push to salsa, is simply
> avoided, because it's not something human needs to remember to do.
As far as I understand this requires:
1. Either one canonical repository on Salsa for each package to which
everyone (including non-team members for NMUs) have full access or
alternatively having some tag2upload-related service having full
access.
2. In case of multiple repositories, all of them to be in sync.
What will tag2upload enforce here? Or is there some alternative
solution that works in the context of NMUs and Git repositories hosted
on Salsa?
Ansgar
