On 2018-08-12 14:35:22 +0200 (+0200), Carsten Schoenert wrote: [...] > that's a feature. > Normally you don't want this and nobody can delete tags unintentionally > as there is normally no reason to change history on a public git tree. > The normal case is to create new tag with the according commit SHA > reference. > > https://docs.gitlab.com/ee/user/project/protected_tags.html > > You can modify the behavior for your git tree, but really be careful if > you remove this protection! As said, you really don't want to do this! :) And probably the biggest reason _why_ you don't want to do this is that tag deletion/replacement doesn't propagate via pull or remote update. You can of course (with appropriate access) delete and replace a tag on the remote but people who have already cloned from it will never see that change (well, except for changes to "lightweight" tags but those are really just a symlink to a ref and not a typical tag object). Treating published tags as if they can't be changed is far more friendly to other users of your repositories. -- Jeremy Stanley
Attachment:
signature.asc
Description: PGP signature