Difference between revisions of "Tags"
From Gcube Wiki
Manuele.simi (Talk | contribs) |
Manuele.simi (Talk | contribs) (→Conventions) |
||
| Line 10: | Line 10: | ||
</source> | </source> | ||
| − | = | + | = Rules = |
| − | * We tag only the | + | * We tag only the master branch |
* Tags are used to mark releases | * 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]'') | * 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]].'' | ''Back to the [[Continuous_Integration_procedure_(2019) | CI guide]].'' | ||
Revision as of 16:06, 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>
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.
