git tag -l not displaying the most recent releases

Question

When I go to deploy my django installation, I get the following error:

local: git tag -l release/beta* | tail -1
run: git checkout release/beta-20120221-150831 
out: error: pathspec 'release/beta-20120221-150831' did not match any file(s) known to git.

The tag exists on my local box, but it doesn't on my staging server. Why? It sends the most recent release "release/beta-20120221-150831".

Did you push the tag to your remote repo? If you never pushed it, the staging server can't see it. — Lily Ballard, Feb 21 '12 at 21:20
Yes, I can view it as a tagged release on github, the staging server can't see it. — paubins, Feb 21 '12 at 21:24
Maybe you haven't actually pulled the tag down to the staging server? — Lily Ballard, Feb 21 '12 at 21:30
I can't pull it down, because it can't see the release. I've done git pull origin . Nothing. — paubins, Feb 21 '12 at 21:33
You're trying to check out a tag, not a branch. Try `git fetch --tags origin` — Lily Ballard, Feb 21 '12 at 23:04

score 8 · Answer 1 · edited May 23 '17 at 10:30

8

Note: as explained in "Does “git fetch --tags” include “git fetch”?", starting git 1.9, one command will be enough to fetch both news commits and tags:

git fetch --tags origin

(Before 1.9, you had to do git fetch + git fetch --tags)

edited May 23 '17 at 10:30

Community

1
1

answered Mar 25 '14 at 12:14

VonC

1,262,500
529
4,410
5,250

git tag -l not displaying the most recent releases

1 Answers1