See below On 15/11/19 05:28, Trout, Diane E. wrote: > ... > I think my habit was to push the tags after the package was actually > accepted since I thought moving a tag can cause conflicts. > > Also in the python team the usually leave the distribution as > UNRELEASED until the final upload and so it's not quite appropriate for > to tag that.
That's a good policy ! Actually you do not need to mark it as released in d/changelog and/or push the debian/... tag. For others to be able to work with your WIP packaging and git-buildpackage, you only need to push the upstream/... tag(s). In my workflow I add the debian/.. tag only at the very last moment for example with: gbp buildpackage --git-tag and all other builds before than one I do with: gbp buildpackage -usc -us If you now delete the debian/... tag and unroll the last commit (you can safely rewrite history of master branch for a personal repo), CI will still work. Paolo -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel