git-tag
Monorepo Version Tags Conventions
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 …
Add new commit to the existing Git 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 …
Can a lightweight tag be converted to an annotated tag?
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 …
GitHub: A tag but not a release
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 …
Git – Checkout a remote tag when two remotes have the same tag name
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 …
What happen to Git tags pointing to a removed commit
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 …
Fetch a single tag from remote repository
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 …
how to close a branch in git
Updated Answer As @user3159253 stated in comments of this answer : git garbage-collects commits which aren’t referenced, directly or indirectly, by a named reference (branch, tag, etc). That is why it is important to leave a reference to a freezed branch. You can tag the tip of the branch by archiving it, and then delete …
Understanding Gitlab CI tags
Tags for GitLab CI and tags for Git are two different concepts. When you write your .gitlab-ci.yml, you can specify some jobs with the tag testing. If a runner with this tag associated is available, it will pickup the job. In Git, within your repository, tags are used to mark a specific commit. It is …