Difference between revisions of "Tags"
From Gcube Wiki
Manuele.simi (Talk | contribs) (→Conventions) |
Manuele.simi (Talk | contribs) |
||
Line 3: | Line 3: | ||
Git supports two types of tags: ''lightweight'' and ''annotated''. In gCube we use lightweight tag to mark a specific point in the repository’s history. | Git supports two types of tags: ''lightweight'' and ''annotated''. In gCube we use lightweight tag to mark a specific point in the repository’s history. | ||
− | |||
The following command creates a tag on the last commit in the current branch: | The following command creates a tag on the last commit in the current branch: | ||
<source lang="bash"> | <source lang="bash"> | ||
− | $ git tag < | + | $ git tag <tagname> |
+ | </source> | ||
+ | |||
+ | However, tags can be created anytime in the project's history. | ||
+ | |||
+ | = Pushing Tags == | ||
+ | You will have to explicitly push tags to a shared server after you have created them. | ||
+ | <source lang="bash"> | ||
+ | $ git push origin <tagname> | ||
</source> | </source> | ||
Revision as of 16:08, 29 May 2019
Creating Tags
Git supports two types of tags: lightweight and annotated. In gCube we use lightweight tag to mark a specific point in the repository’s history.
The following command creates a tag on the last commit in the current branch:
$ git tag <tagname>
However, tags can be created anytime in the project's history.
Pushing Tags =
You will have to explicitly push tags to a shared server after you have created them.
$ git push origin <tagname>
Rules
- We tag only the master branch
- Tags are used to mark releases
- Tags are applied after the related gCube release is declared closed
- The tag name must be in the format "vX.Y" or "vX.Y.Z" (where X,Y,Z are follow the versioning schema major.minor[.build])
TBP
Back to the CI guide.