Hi, On Thu, Mar 20, 2025 at 02:39:44PM -0400, Jeremy Bícha wrote: > On Thu, Mar 20, 2025 at 2:37 PM Guido Günther <a...@sigxcpu.org> wrote: > > > > Hi, > > On Thu, Mar 20, 2025 at 02:18:24PM -0400, Jeremy Bícha wrote: > > > Source: git-buildpackage > > > Version: 0.9.37 > > > > > > Sometimes I forget to git pull before I gbp push. This is a problem if > > > I have tagged a release. gbp push pushes the git tags first and then > > > errors on pushing the branches. > > > > > > I imagine if git-buildpackge could push the branches first and if the > > > branches fail, then it could intentionally not push the git tags. > > > > > > This would make it easier to fix the situation locally without needing > > > to delete the erroneous git tag that has been pushed. > > > > This is already possible by setting the tag empty. See > > > > > > https://salsa.debian.org/DebianOnMobile-team/dom-tools/-/blob/main/release-dom-component?ref_type=heads#L161 > > > > Updates to the documentation are welcome. > > This is a request for a better default, not for documentation. If > there is a problem pushing to one of the branches, there could be a > problem with a tag also. Therefore I would expect git-buildpackage to > not push the tag.
I'd argue that pushing tags first *is* the better default as it ensures tags become public if present. Once can always construct branches from tags but not the other way round. I might not understand your use case correctly. If the issue is that pushing the same tag again fails than this should become idempotent rather than switching the order. (no idea how this got `-done` added to the address, ropening) Cheers, -- Guido > > Thank you, > Jeremy Bícha >
