3 ms·

While this may be technically correct, the general git-community at large mostly treats tags as immutable (contrary to docker, for example). Release branches a

While this may be technically correct, the general git-community at large mostly treats tags as immutable (contrary to docker, for example). Release branches are typically the mutable reference. So I would create a 'v2' release branch, but not a 'v2' tag which gets updated. Also, by convention, git references starting with 'v' are typically immutable tags and not branches. But, even given the above, the git-community at large knows that tags can be mutable, and so if we care about that, we reference the sha (malicious collisions excepted).

ptx 2y ago
That's a good point and might explain the source of this confusion. Actions on GitHub can come from either Docker or a Git repo, using exactly the same syntax [0], so the tag can be either a Docker tag or a Git tag. [0] https://docs.github.com/en/actions/writing-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsuses https://docs.github.com/en/actions/writing-workflows/workflo...