Pushing deployment tag fails when other unrelated tags already exist on remote

mydrive / capistrano-deploytags

Add timestamped Git tags for each environment on deployment

BSD 2-Clause "Simplified" License

123 stars 20 forks source link

Pushing deployment tag fails when other unrelated tags already exist on remote #24

Open ghost opened 9 years ago

ghost commented 9 years ago

Consider pushing the just created deploy tag only or force the push. Log:

failed to push some refs ...
Updates were rejected because the tag already exists in the remote

relistan commented 9 years ago

Hi, thanks for the report. I'm a little confused because I don't see how you got it into that state?

ghost commented 9 years ago

Two situations come to my mind:

tag a commit, deploy, drop tag, tag another commit, deploy
dev1 tags a commit, deploy, dev2 tags a commit, deploy

Our team usually does not push tags, so in the course of several months one could had created various tags on his machine and at the moment of deployment these are all pushed unintentionally where only newly created deployment tag was intended to be pushed.