Open Stack

On 2018-09-24 11:43:35 -0400 (-0400), Thomas Bachman wrote:
> Sorry for the list-wide distribution on this -- I wasn't sure
> where to start. I have a question about process/procedure. I've
> carelessly created a tag against the wrong branch in an upstream
> repo -- in this case, the 0.16.0 tag in the
> python-group-based-policy-client repo. Is there a process for tag
> deletion in upstream repos?

One of the reasons we strongly remind project drivers to carefully
check what they're tagging before pushing is that Git tags (aside
from so-called "lightweight tags" which are really just symlinks)
effectively aren't deletable. Consider them permanent once pushed.

It's true that you _can_ delete a tag from a remote, but such
deletions don't propagate via pull or remote update. As a result,
downstream consumers who have pulled the tag in question (including
our CI system) won't see the removal of that tag and will continue
to behave as if it's still present.

If at all possible, consider solutions which involve pushing an even
newer tag in the wake of the accidental one, so that the previous
tag will at least appear to be obsolete.
-- 
Jeremy Stanley
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-infra/attachments/20180924/41205ab1/attachment.sig>