You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Retagging, even if the git SHA hasn't changed, is a deliberate design decision. Consider a production deployment where we add a server to an existing cluster. We need to deploy the code to this new server, but the git SHA hasn't changed since the last deploy to a different set of servers. We absolutely want to know about the two distinct deploys, even though the code hasn't changed, so we tag all deploys.
It would be great if redeploying commits wouldn't produce more tags.
Thank you for your useful script!
The text was updated successfully, but these errors were encountered: