I have faced same issue and it was because of copy-paste. Typing by hand solves the issue. If you don’t want type all the command by hand try to go at the starting of the command after pasting it to the console and click backspace button multiple times. This should remove hidden characters and should … Read more
You want to use the for-each-ref command. Unfortunately, it’s only slightly less user friendly than filter-branch Note that information like tag date and the tagger is only available for annotated tags. Below is a basic prototype. Note that the format= can be an entire shell script of its own, and probably should be depending on … Read more
tags are organized in directories and files (all git references are, run tree .git/refs/tags to see that), so I would suggest naming the tags : myapp1/1.0.0 myapp1/1.0.1 … myapp2/2.1.0 myapp2/2.2.0 … This will group versions for each app together, and some commands will treat the numbers “naturally” : # list tags, sorted by version number … Read more
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 … Read more
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 … Read more
GitHub, by default, creates a “release” point when you push a tag (like you can see in my project), but that doesn’t mean it creates an actual release. By default, a tag has one deliverable associated to the tag, and that is the compressed sources of the repo. Creating a release means associating other deliverables … Read more
Executive summary: what you want to achieve is possible, but first you must invent remote tags. You do this with a series of refspecs, one for each remote. The rest of this is about what these are, how they work, and so on. Your question asks about checking out a “remote tag”, but Git does … Read more
What happen to tag t? Let’s say you created branch x from a commit E and then tagged that commit with tag t. E.g. x (branch) | V A—–B——C——D——E ^ | t (tag) If you remove branch x nothing happens to tag t. git branch -D x The tag still points to commit E. A—–B——C——D——E … Read more