You can tag a revision right after your commit or later (after a push). Then, you can push your tag with: git push origin [tagname]. So, yes, your sequence is ok. Take a look at this, for more details: https://git-scm.com/book/en/v2/Git-Basics-Tagging.
Unfortunately, git pull doesn’t fetch tags by default. You need to run git fetch –tags, and then you’ll have them. The default behavior of git pull and git fetch is to only retrieve tags that are directly accessible by the current references. If any tags are not, then those are not fetched. Passing –tags to … Read more
Update for Git 2.23 (Q3 2019), you now have git config tag.gpgSign true! Original answer (June 2018) While there is no “signed by default” mode for git tag, the documentation mentions: Once you have a private key to sign with, you can configure Git to use it for signing things by setting the user.signingkey config … Read more
I’m not sure what version of git this requires, but with recent versions you can also do: git tag -l –format=”%(contents)” <tag name> to get only the tag message by itself.
You can use the following to see the tags that exist locally but not in the specified remote: git show-ref –tags | grep -v -F “$(git ls-remote –tags <remote name> | grep -v ‘\^{}’ | cut -f 2)” Note that git ls-remote shows both the annotated tag and the commit it points to with ^{}, … Read more
I’d say that with published work, you should just always use annotated tags. That extra information is never going to harm you. Lightweight tags strike me as being more for when you’re being lazy. Maybe a temporary tag (just make sure you don’t accidentally push it; really you could just use a branch), or maybe … Read more
A more direct way of getting the same info is: git cat-file tag <tagname> This uses a single command and avoids the pipe. I used this in a bash script as follows: if git rev-parse $TAG^{tag} — &>/dev/null then # Annotated tag COMMIT=$(git rev-parse $TAG^{commit}) TAGGER=($(git cat-file tag $TAG | grep ‘^tagger’)) N=${#TAGGER} # Number … Read more
The closest option may be: git push –follow-tags Push all the refs that would be pushed without this option, and also push annotated tags in refs/tags that are missing from the remote but are pointing at committish that are reachable from the refs being pushed.
After Creating the Tag Right click in the repo folder From the context menu select “Git Sync…” Change the “Push” drop down to “Push tags” (this will initiate the push)
The answers given are basically correct. As tags and branches are just names for objects, there is a simpler way without touching current work area: git tag <name_for_tag> refs/heads/<branch_name> # or just git tag <name_for_tag> <branch_name> git branch -d <branch_name> Or even do it to remote server without touching local repository at all: git push … Read more