git-tag

I have a git repository which uses a submodule which I'd like to point at an annotated tag, but when I do git submodule update new tags don't get fetched. I can get new tags in the submodule by cd-ing into the submodule and doing a git fetch --tags there, but I'd really like to do all of this from the outside as it's scripted. I can't find anything in the git documentation suggesting a way to get git submodule update to include tags (my git version is 1.7.3.5). Obviously there is another possibility - to point the submodule at the commit which the tag points to rather than the tag itself, but

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't let me do: git checkout tags/2.3.18 How can I fetch a single tag and then perform a checkout? git fetch origin refs/tags/1.0.0 This fails because it doesn't write a local reference: it obtains the remote's refs/tags/1.0.0 , and any tag object(s), commits, etc., required to go with it; it drops those into FETCH_HEAD (as all git fetch commands always do); and ... that's it. It never creates reference refs/tags/1.0.0 in your repository, even though it got

A pre-release version MAY be denoted by appending a dash and a series of dot separated identifiers immediately following the patch version. Examples: 1.0.0-alpha, 1.0.0-alpha.1, 1.0.0-0.3.7, 1.0.0-x.7.z.92. semver.org For the purpose of disambiguation, what would be a "proper" way to tag a release commit (commit from the master branch)? Some ideas v1.7.2-release v1.7.2-master v1.7.2-prod v1.7.2-official v1.7.2-stable github.com/antirez/redis/tags You can choose a policy similar to Git itself (see its tags in the GitHub repo ): v1.7.2-rc0 v1.7.2-rc1 v1.7.2-rc2 v1.7.2-rc3 v1.7.2 The idea (as

I have created a Git tag as v1.1 using git tag -a v1.1 -m 'my version 1.1' and I pushed that tag. Later, I made some changes related to v1.1 . Now when I push new changes and check the git tag using git describe it is showing me v1.1-g2dcc97 . How can I add my new commit to the existing tag? You can't put a new commit into an existing tag without breaking an important Git guideline: Never(*) modify commits that you have published. Tags in Git aren't meant to be mutable. Once you push a tag out there, leave it alone. You can, however, add some changes on top of v1.1 and release something like

I'm trying to tag the git repo of a ruby gem in a Bamboo build. I thought doing something like this in ruby would do the job `git tag v#{current_version}` `git push --tags` But the problem is that the repo does not have the origin. somehow Bamboo is getting rid of the origin Any clue? Yes, if you navigate to the job workspace, you will find that Bamboo does not do a straightforward git clone "under the hood", and the the remote is set to an internal file path. Fortunately, Bamboo does store the original repository URL as ${bamboo.repository.git.repositoryUrl}, so all you need to do is set a

so the git tag command lists the current git tags tag1 tag2 git tag -n prints tag's message tag1 blah blah tag2 blah blah What's the best way to get the hash of tag1 & tag2 ? How about this? git show-ref --tags The git tag command is underdeveloped. A lot is desired but missing in it, like full tag details and tags in the commit history order. I like this instead, which gives exactly what I want but can't get from git tag : git log --oneline --decorate --tags --no-walk This gives a very nice color-coded view of the tags in the reverse chronological order (as it would be in the full log). That

I'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? If you create a tag by e.g. git tag v1.0 the tag will refer to the most recent commit of the branch you are currently on. You can change branch and create a tag there. You can also just refer to the other branch while tagging, git tag v1.0 name_of_other_branch which will create the tag to