git-tag

Long story short I'm writing a script to migrate a very large project from (gasp) Microsoft SourceSafe to Git and I'm trying to retain the authors of the SourceSafe project's labels(which are essentially tags in Git). I know you can modify the author and committer name/date of a Git Commit but can you do the same to a Git Tag? TL;DR Re-create the tags with the new desired data. But if anyone else had them before, they may not accept your new ones. Or they may! It's up to them , though. Description I know you can modify the author and committer name/date of a Git Commit Actually, you can't ,

I understand how it is possible to tag a blob, or a tree, or even another annotated tag, using a git tag. I understand the architecture and conceptual design that makes this possible. However, I'm having trouble thinking of real life applications of this (or "real workflow" applications). Searching here on Stack Overflow I only found one answer that mentions tagging non-commit objects, with advice not to do so . Under what possible circumstances could it ever be appropriate to tag a non-commit object? Tagging trees or blobs may be appropriate temporarily in long-running utility programs that

I am looking for the best and safest way to convert a git branch to a git tag. When porting over a svn repository by hand, I basically copied over all our branches and we had a branch for each minor release (1.1, 1.2, 1.3) which in all honesty probably was not the best way of doing that but for the sake of speed, I was more comfortable with branches than tags at the time. I now have branches 1.5, 1.6, 1.7, 1.8 however since we only ever have 1 version of the code deployed at any given time, I probably only need the last version to be a branch incase any hot fixes need to go into that version

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 "git describe", and how to fix this? The v2.0 tag is already pushed, so I am guessing that I can't just delete and re-add it. git describe uses only annotated tags by default. specify the --tags option to make it use lightweight tags as well make sure you've checked out the correct commit ( git rev-parse HEAD ). annotated tags are created with git tag -a . if you do git show <tagname> and you see

How do I check out version version/tag 1.1.4 of the rspec bundle ? cd ~/Library/Application\ Support/TextMate/Bundles/ git clone git://github.com/rspec/rspec-tmbundle.git RSpec.tmbundle osascript -e 'tell app "TextMate" to reload bundles' Clone the repository as normal: git clone git://github.com/rspec/rspec-tmbundle.git RSpec.tmbundle Then checkout the tag you want like so: git checkout tags/1.1.4 This will checkout out the tag in a 'detached HEAD' state. In this state, "you can look around, make experimental changes and commit them, and [discard those commits] without impacting any branches

I have a local Git repository which contains three annotated tags: v0.1.0 , v0.1.1 , and v0.1.2 . When I view my project's history with gitk ( Repository → Visualize master's history ), I can see each tag assigned to the proper commit. However, when I try to checkout my tags in Git GUI ( Branch → Checkout... → Tags ), the tag for v0.1.1 doesn't appear. When I went to check each tag in gitk, I noticed that the tag details were slightly different. The details for v0.1.0 and v0.1.2 listed them as type commit , while the tag for v0.1.1 was listed as type tag . It's worth noting that I've rewrote

I've tagged a commit with a lightweight tag, and pushed that tag to a remote repo, shared with other developers. I have now realised I should have annotated it so that it appears in git describe . Is there a way to convert it/re-tag the commit without breaking things? A lightweight tag is just a 'ref' that points at that commit. You can force-create a new annotated tag on top of the old tag: git tag -a -f <tagname> <tagname> As of Git v1.8.2, you need to use --force to replace any tags on a remote with git push , even if you are replacing a lightweight tag with something that is effectively a