Difference between revisions of "Tags"
From Gcube Wiki
Manuele.simi (Talk | contribs) (Created page with "== Creating Tags == Git supports two types of tags: ''lightweight'' and ''annotated''. In gCube we use annotated tag to mark a specific point in the repository’s history....") |
Manuele.simi (Talk | contribs) |
||
Line 1: | Line 1: | ||
− | + | = Creating Tags = | |
− | Git supports two types of tags: ''lightweight'' and ''annotated''. In gCube we use | + | 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. |
− | + | ||
− | + | ||
Tags can be created anytime in the project's history. | Tags can be created anytime in the project's history. | ||
+ | The following command creates a tag on the last commit in the current branch: | ||
<source lang="bash"> | <source lang="bash"> | ||
− | git tag | + | $ git tag <my tag> |
</source> | </source> | ||
+ | = Conventions = | ||
+ | * We tag only the release branch | ||
+ | * Tags are used to mark releases | ||
+ | * 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 | TBP | ||
+ | ''Back to the [[Continuous_Integration_procedure_(2019) | CI guide]].'' |
Revision as of 16:04, 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.
Tags can be created anytime in the project's history. The following command creates a tag on the last commit in the current branch:
$ git tag <my tag>
Conventions
- We tag only the release branch
- Tags are used to mark releases
- 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.