New feature "Block new tags that differ only by case" gives error on force updating existing tags

Hi,

When the new feature “Block new tags that differ only by case” is enabled, and you try to push an update to an existing tag, it fails because it says it doesn’t allow changes that only differ in case. It seems like a check is missing to allow force pushes when the tag is identical. If the tag you’re pushing and the tag it found are exactly the same (even by case), it shouldn’t throw an error. We specifically ran into this problem when our pipeline tried to update the tags “latest”. As a workaround we’ve disabled this feature for now.

remote: 
remote: Control Freak - Rejected new tag: "latest".        
remote: -----        
remote: Rejected new tag: "latest".        
remote: New tags must differ by more than just case-sensitivity.        
remote: Existing tag: "latest"        
remote: 
remote: To delete your local copy of this rejected tag:        
remote: 
remote: git tag -d latest        
remote: -----        
remote:

‌

Comments (3)