How do you delete a Git tag that has already been pushed?

How to delete a remote tag?

Say I do the following:

 1. Create branch `X`
 2. Create Tag `t` (to branch `X`)
 3. Push
 4. Remove branch `X`

What happen to tag `t`? is it just floating there? is it considered as garbage?

Should I remove all tags pointing at branch before removing the branch itself?

### Reference 
From [Git Basics - Tagging](https://git-scm.com/book/en/v2/Git-Basics-Tagging):

&gt; Git uses two main types of tags: lightweight and annotated. A
&gt; lightweight tag is very much like a branch that doesn’t change – **it’s
&gt; just a pointer to a specific commit.**

What happen to Git tags pointing to a removed commit

This command fetches **all** tags:

    git fetch origin --tags

This command fetches a specific tag:

    git fetch origin refs/tags/1.0.0

**But** that doesn&#39;t let me do:

    git checkout tags/2.3.18

How can I fetch a single tag and then perform a checkout?

Fetch a single tag from remote repository

I want to delete all the tags from a Git repository. How can I do that?

Using `git tag -d tagname` delete the tag `tagname` locally, and using `git push --tags` I update the tags on the git provider.

I tried:

    git tag -d *

But I see that `*` means the files from the current directory.

    $ git tag -d *
    error: tag &#39;file1&#39; not found.
    error: tag &#39;file2&#39; not found.
    ...

Consider I have a lot of tags, and I want to delete them, all.

Delete all tags from a Git repository

I have a repository in GitHub and I need to **tag** it.   
I tagged in a shell, but on **GitHub**, it is not showing up. 

Do I have to do anything else?

The command I used in the shell is:

    git tag 2.0

And now when I type `git tag` it shows:

    2.0

So it seems like tags are present, correct?

The repository is: [https://github.com/keevitaja/myseo-pyrocms][1].

How do I make this tag show up on GitHub? Where are my tags?

  [1]: https://github.com/keevitaja/myseo-pyrocms



Create a tag in a GitHub repository

I had hoped this would work:

    git checkout remote/tag_name

but it doesn&#39;t. This does:

    git checkout tags/tag_name

but I&#39;m doing something weird where I have a lot of remotes, and I&#39;m worried about what happens if two remotes have the same tag. Is there a way to specify the remote when checking out the tag?

Git - Checkout a remote tag when two remotes have the same tag name

I want to tag a certain commit. When I push the tag, GitHub assumes it&#39;s a release, I don&#39;t want that.

Is there a way to just push the tag without releasing?

GitHub: A tag but not a release

A nice and simple question - is the function of &quot;git fetch&quot; a strict sub-set of `git fetch --tags`?

I.e. if I run `git fetch --tags`, is there ever a reason to immediately run `git fetch` straight afterward?


What about `git pull` and `git pull --tags`? Same situation?



Does &quot;git fetch --tags&quot; include &quot;git fetch&quot;?

We are new to git, and I want to set a tag at the beginning of our repository. 
Our production code is the same as the beginning repository, but we&#39;ve made commits since then.
A tag at the beginning would allow us to &quot;roll back&quot; production to a known, stable state.

So how to add a tag to an arbitrary, older commit?

How to tag an older commit in Git?

I&#39;m having trouble finding out which tag is currently checked out.

When I do:  

    git checkout tag1
    git branch

I can&#39;t seem to find out which tag I&#39;m on. It only logs:

    * (no branch)
    master

Is it possible to find out which tags are checked out? In the above example, this would be `tag1`.



Show which git tag you are on?

I&#39;ve seen a lot of projects using `v1.2.3` as the naming convention for tags in git. I&#39;ve also seen some use `1.2.3`. Is there an officially endorsed style, or are there any good arguments for using either?

Is there a standard naming convention for git tags?

We have several annotated tags in our Git repository. The older tags have bogus messages that we would like to update to be in our new style.

    % git tag -n1
    v1.0 message
    v1.1 message
    v1.2 message
    v2.0 Version 2.0 built on 15 October 2011.

In this example, we would like to make v1.x messages look like the v2.0 message. How would we do this?

How do I edit an existing tag message in Git?

I created a tag on the master branch called `v0.1` like this:

    git tag -a v0.1

But then I realized there were still some changes I needed to merge into master for release 0.1, so I did that. But now my `v0.1` tag is stuck on (to invoke the post-it note analogy) the wrong commit. I want it to be stuck on the most recent commit on master, but instead it is stuck on the second most recent commit on master.

How can I move it to the most recent commit on master?

How can I move a tag on a git branch to a different commit?

How do I check out version version/tag 1.1.4 of the [rspec bundle][1]?

    cd ~/Library/Application\ Support/TextMate/Bundles/
    git clone git://github.com/rspec/rspec-tmbundle.git RSpec.tmbundle
    osascript -e &#39;tell app &quot;TextMate&quot; to reload bundles&#39;


  [1]: https://github.com/rspec/rspec-tmbundle

Switch to another Git tag

Since I created my repository it appears that the tags I have been
creating are not pushed to the repository. When I do `git tag` on the
local directory all the tags are present, but when I logon to the
remote repository and do a `git tag`, only the first few show up.

What could the problem be?.

Do git tags get pushed as well?

I want to force push, for example, my tag `1.0.0` to my remote `master` branch.

I&#39;m now doing the following:

    git push production +1.0.0:master

***I want to force the push***, because all I care about is that the code inside the `1.0.0` tag is pushed to the `master` branch on the remote repository.

What am I doing wrong?

### Update #1  
When I SSH into my server where my [Git][1] repository is and execute `git branch -l`, I don&#39;t see the `master` branch listed either.

### Update #2  
After running `git tag -l` from inside the remote Git repository, I see that `master` is listed, meaning that when I ran the following:

    git push production 1.0.0:master

It actually pushed the tag and ***created a tag named*** `master` rather than ***a new branch***.

I want to basically push the ***contents*** of the tag `1.0.0` into the `master` branch of the remote Git repository.

  [1]: http://en.wikipedia.org/wiki/Git_%28software%29


How do you push a Git tag to a branch using a refspec?

I&#39;m currently working with a repository that has multiple branches.

When I create a tag, does that tag refer to the then-current branch?

In other words: Whenever I create a tag, do I need to switch to the desired branch and tag inside that branch so that the tag refers to that branch at that point in time?

Do Git tags only apply to the current branch?

I&#39;m trying to find the syntax for merging a tagged commit onto another branch. I&#39;m guessing that it&#39;s straight forward but my feeble search attempts aren&#39;t finding it.

How do I merge a git tag onto a branch

In my repository, I have created tags using the following commands. 

    git tag v1.0.0 -m &#39;finally a stable release&#39;
    git tag v2.0.0 -m &#39;oops, there was still a major bug!&#39;

How do you list all the tags in the repository?

How to list all Git tags?

I&#39;m developing a deployment script for my git project and I just started using tags. I&#39;ve added a new tag called `v2.0`:

    git tag -a v2.0 -m &quot;Launching version 2.0&quot;

And I&#39;ve pushed this tag to the remote repository

    git push --tags

When I try to execute the deployment script and check out the `v2.0` tag I get this message:

&gt; *You are in &#39;detached HEAD&#39; state. You can look around, make experimental changes and commit them, and you can discard any commits
&gt; you make in this state without impacting any branches by performing
&gt; another checkout. If you want to create a new branch to retain commits
&gt; you create, you may do so (now or later) by using -b with the checkout
&gt; command again. Example:   git checkout -b new_branch_name HEAD is now
&gt; at*

Is that normal? The repository is in limbo because if I do:

    git branch

I get this output:

    * (no branch)
      master

Sorry if this is obvious but I couldn&#39;t figure it out.

Checking out Git tag leads to &quot;detached HEAD state&quot;

I get the following error after I run the steps below:


    To git@provider.com:username/repo-name.git
     ! [rejected]        dev -&gt; dev (already exists)
    error: failed to push some refs to &#39;git@provider.com:username/repo-name.git&#39;
    hint: Updates were rejected because the tag already exists in the remote.

1. Created the repository
2. Cloned the repo on the local machine.
3. Modified the README file, commited the changes and pushed the commit.
4. Created tag `dev`: `git tag dev`
5. Pushed tags: `git push --tags`
6. Modified the README file, commited the changes and pushed the commit.
7. Deleted tag `dev` , created it again and pushed tags:

        git tag -d dev
        git tag dev
        git push --tags

Why is this happening?

I am on Mac. My friends that use Linux (Ubuntu) don&#39;t have this problem. I know that I can use `git push --tags -f` to force the tag update, but this is dangerous (e.g. rewriting a commit made by mistake only in the tag, not in the branch). 

“tag already exists in the remote&quot; error after recreating the git tag

I am having some difficulty understanding how to use *tags* versus *branches* in [tag:Git].

I just moved the current version of our code from [tag:CVS] to [tag:Git], and now I&#39;m going to be working on a subset of that code for a particular feature. A few other developers will be working on this as well, but not all developers in our group are going to care about this feature. Should I be creating a branch or a tag? In what situations should I be using one versus the other?

How is a tag different from a branch in Git? Which should I use, here?

when I checkout remote git tag use command like this:

    git checkout -b local_branch_name origin/remote_tag_name

I got error like this:
    
&gt; error: pathspec `origin/remote_tag_name` did not match any file(s) known to git.

I can find remote_tag_name when I use git tag command.

What is git tag, How to create tags &amp; How to checkout git remote tag(s)

I have cloned a remote Git repository to my laptop, then I wanted to add a tag so I ran

    git tag mytag master

When I run `git tag` on my laptop the tag `mytag` is shown. I then want to push this to the remote repository so I have this tag on all my clients, so I run `git push` but I got the message:

&gt; Everything up-to-date

And if I go to my desktop and run `git pull` and then `git tag` no tags are shown. 

I have also tried to do a minor change on a file in the project, then push it to the server. After that I could pull the change from the server to my Desktop computer, but there&#39;s still no tag when running `git tag` on my desktop computer.

How can I push my tag to the remote repository so that all client computers can see it?

How do you push a tag to a remote repository using Git?

I&#39;d like to create a new master branch from an existing tag. Say I have a tag `v1.0`. How to create a new branch from this tag?

How to create a new branch from a tag?

I&#39;ve been using git for about a year and would like to use tagging to, well, tag commits at different versions. I&#39;ve found lots of info on the commands to use to work with tags, but what I&#39;d like to know is why use tagging at all if I can just create a new branch called `1.1.0` and not have to cloud my mind with a whole new set of git commands?

There has to be a lot of good reasons for tagging rather than branching but I&#39;d like to know what those advantages are.

Why should I use tags vs. release/beta branches for versioning?

What&#39;s the simplest way to get the most recent tag in Git?

    git tag a HEAD
    git tag b HEAD^^
    git tag c HEAD^
    git tag

output:

    a
    b
    c

Should I write a script to get each tag&#39;s datetime and compare them?

How can I get the latest tag name in current branch in Git?

so the `git tag` command lists the current git tags

    tag1
    tag2

`git tag -n` prints tag&#39;s message

    tag1  blah blah
    tag2  blah blah



_What&#39;s the best way to get the hash of tag1 &amp; tag2 ?_

Git Tag list, display commit sha1 hashes

We use tags in git as part of our deployment process.  From time to time, we want to clean up these tags by removing them from our remote repository.

This is pretty straightforward.  One user deletes the local tag and the remote tag in one set of commands.  We have a little shell script that combines both steps.

The 2nd (3rd, 4th,...) user now has local tags that are no longer reflected on the remote.  

I am looking for a command similar to `git remote prune origin` which cleans up locally tracking branches for which the remote branch has been deleted.

Alternatively, a simple command to list remote tags could be used to compare to the local tags returned via `git tag -l`.

Remove local git tags that are no longer on the remote repository

I have a project that is using git and have tagged all the releases with a tag.

    $ git tag
    v1.0.0
    v1.0.1
    v1.0.2
    v1.0.3
    v1.1.0

My goal is to list the releases and release dates in a web interface (tag/commit date = release date). Currently we list all the releases by using `git tag`.

**How can I get the time and date for when the tag was made (or the commit it points to)?**

Get the time and date of git tags

I&#39;m trying to figure out how I can download a particular tag of a Git repository - it&#39;s one version behind the current version.

I saw there was a tag for the previous version on the git web page, with object name of something long hex number. 

But the version name is &quot;`Tagged release 1.1.5`&quot; according the site.

I tried a command like this (with names changed):

    git clone http://git.abc.net/git/abc.git my_abc

 
And I did get something - a directory, a bunch of subdirectories, etc.  

If it&#39;s the whole repository, how do I get at the version I&#39;m seeking? If not, how do I download that particular version? 







Download a specific tag with Git

I have a bunch of unannotated tags in the repository and I want to work out which commit they point to. Is there a command that that will just list the tags and their commit SHAs? Checking out the tag and looking at the HEAD seems a bit too laborious to me.

## Update

I realized after I went through the responses that what I actually wanted was to simply look at the history leading up to the tag, for which `git log &lt;tagname&gt;` is sufficient. 

The answer that is marked as answer is useful for getting a list of tags and their commits, which is what I asked. With a bit of shell hackery I&#39;m sure it&#39;s possible to transform those into SHA+Commit message.

How to tell which commit a tag points to in Git?

I type `git tag` and it lists my current tags:

    1.2.3
    1.2.4

How can I determine which of these is annotated, and which is lightweight?

How can I tell if a given git tag is annotated or lightweight?

I have got a error message while creating tag containing `[` character:

&gt; fatal: &#39;[&#39; is not a valid tag name.

Question: are there any rules for tags in the git?

What names are valid git tags?

Say I&#39;ve forked a node module with a bugfix and I want to use my fixed version, on a feature branch of course, until the bugfix is merged and released. 

How would I reference my fixed version in the `dependencies` of my `package.json`?

Depend on a branch or tag using a git URL in a package.json?

If I want to tag the current commit. I know both of the following command lines work:

    git tag &lt;tagname&gt;

and

    git tag -a &lt;tagname&gt; -m &#39;&lt;message&gt;&#39;

What is the difference between these commands?


What is the difference between an annotated and unannotated tag?

I want git to list all tags along with the full annotation or commit message. Something like this is close:

    git tag -n5

This does exactly what I want except that it will only show up to the first 5 lines of the tag message.

I guess I can just use a very large number. What is the highest number I can use here? Is it the same on every computer?

**UPDATE**: I have had much time to think about this, and now I think I don&#39;t necessarily want to show the entirety of each message if some of them are extraordinarily long. I didn&#39;t really have any particular need that required me to see massive messages (other than my own propensity to be long winded in everything I write, including tag messages). I just didn&#39;t like the idea that it was not necessarily going to show me the whole message, as that made me feel like it was hiding information from me. But too much information can also be a bad thing.

How to list all tags along with the full message in git?

In the following lines:

    $ git tag -n1
    v1.8        Tagged the day before yesterday
    v1.9        Tagged yesterday
    v2.0        Tagged today
    $ git describe
    v1.9-500-ga6a8c67
    $ 

Can anyone explain why the v2.0 tag is not used by &quot;git describe&quot;, and how to fix this? The v2.0 tag is already pushed, so I am guessing that I can&#39;t just delete and re-add it.


&quot;git describe&quot; ignores a tag

Is there a way to keep my local git tags in lockstep with a remote&#39;s tags? That is -- not only get new tags when created (as usual, when `fetch`-ing/`pull`-ing), but also prune tags no longer on a remote and also delete existing tags when someone else `git push -f`&#39;s a tag.
I know I can `git fetch remotename` followed by `git remote prune remotename` to achieve similar behaviour for branches.

In git, how do I sync my tags against a remote server?

On git hub I re-added the tag by doing: 
    
    git tag -d 12.15
    git push origin :refs/tags/12.15
    git tag -a 12.15 -m &#39;12.15&#39;
    git push --tags

The tag is still referring to the old tag on github, but locally it is done right.

UPDATE: It seems github is listing the last commit wrong, but downloading it correctly.

git tag delete and re-add

I have a repo [iontech/Anagen][1] forked from [agiliq/Anagen][2]

I made a few commits to my fork and added a tag. Then I opened a Pull Request. This Pull Request includes only my commits.

How do I include the tag I&#39;ve created into the Pull Request?


  [1]: http://github.com/iontech/Anagen
  [2]: http://github.com/agiliq/Anagen

Adding Tags to a Pull Request

From [git-clone(1) Manual Page][1]

&gt; `--branch` can also take tags and detaches the HEAD at that commit in the resulting repository.

I tried  

    git clone --branch &lt;tag_name&gt; &lt;repo_url&gt;

But it does not work. It returns:  

    warning: Remote branch 2.13.0 not found in upstream origin, using HEAD instead

How to use this parameter?

  [1]: http://git-scm.com/docs/git-clone

How to clone a specific Git tag

I switched from Subversion to Git as my day-to-day VCS last year and am still trying to grasp the finer points of &quot;Git-think&quot;.

The one which has been bothering me lately is &quot;lightweight&quot; vs. annotated vs. signed tags.  It seems pretty universally accepted that annotated tags are superior to lightweight tags for all real uses, but the explanations I&#39;ve found for why that&#39;s the case always seem to boil down to either [&quot;because best practices&quot;](https://stackoverflow.com/questions/4092640/in-what-circumstances-should-i-add-the-a-flag-to-the-git-tag-command) or [&quot;because they&#39;re different&quot;](http://www.rockstarprogrammer.org/post/2008/oct/16/git-tag-does-wrong-thing-default/).  Unfortunately, those are very unsatisfying arguments without knowing *why* it&#39;s best practices or how those differences are *relevant* to my Git usage.

When I first switched to Git, lightweight tags seemed to be the best thing since sliced bread; I could just point at a commit and say &quot;that was 1.0&quot;.  I&#39;m having trouble grasping how a tag could ever need to be more than that, but I certainly can&#39;t believe that the Git experts of the world prefer annotated tags arbitrarily!  So what&#39;s all the hubbub about?

*(Bonus points: Why would I ever need to sign a tag?)*

**EDIT**

I&#39;ve been [successfully convinced](https://stackoverflow.com/questions/4971746/why-should-i-care-about-lightweight-vs-annotated-tags/4971817#4971817) that annotated tags are a Good Thing — knowing who tagged and when is important!  As a follow-up, any advice on good tag annotations?  Both `git tag -am &quot;tagging 1.0&quot; 1.0` and trying to summarize the commit log since the previous tag feel like losing strategies.

Why should I care about lightweight vs. annotated tags?

How to get last tag from a (non checked-out) remote repo?

On my local copy I use `describe`

    git describe --abbrev=0 --tags

But I cannot use `describe` with remote storage

Get last git tag from a remote repo without cloning

Today I was looking through the logs for a project and realized that I fat fingered a tag name some time ago. Is there some way to rename the tag? Google hasn&#39;t turned up anything useful.

I realize I could check out the tagged version and make a new tag, I even tried that. But that seems to create a tag object that isn&#39;t quite right. For one,

    git tag -l

lists it out of order relative to all of the other tags. I have no idea if that&#39;s significant, but it leads me to believe that the new tag object isn&#39;t quite what I want. I can live with that, because I really only care that the tag name matches the documentation, but I&#39;d rather do it &quot;right&quot;, assuming there is a right way to do this.

How do you rename a Git tag?

I have a simple question about tagging different versions of my project with git. If I just completed my 1.1 branch and plan to merge it into master, should I tag this branch as 1.1 before I merge it, or should I merge it to master and then tag it as 1.1? Would it make a difference either way? Maybe one way is preferred? Thanks.

Git tag before or after merge?

I have a tag already pushed onto the remote. When another user creates the same tag and tries to push, the push will fail because the tag already exists on the remote.

But I thought if I did `--f force tag push`, it should work. But that is not what I see.

I think I have to do this.

     Create tag
     Push tag -&gt; If push fails -&gt; Delete tag on remote
                               -&gt; push tag again.

Is this correct? Isn`t force pushing a tag supposed to take care of this?

I am using annotated tags with 
      
     git -a v1.0 -f -m &quot;message&quot;



Git force push tag when the tag already exists on remote

When I know I won&#39;t use a branch any more is it possible to close or lock it? Actually I would like to close a branch but I don&#39;t think it is possible to close a branch with GIT. what about the delete. What happens to my history when I delete a branch? 

All Git Tag Solutions on Gang of Coders

Total of 48 Git Tag Solutions