![]() ![]() ![]() Please, verify push permissions to GerritHub and (if required) to GitHub. Master - When required, the changes from the devel branch merged into a master branch and tagged with a version.įor more details, refer to the git tagging doc. The features branches are created from and merged to the devel branch once tested and reviewed.Īll the new patches merged into devel branch and running for a while in order to make sure there is no errors. Our git repository has two major branches.ĭevel - All the development work starts from the devel branch. Git tag - git tag is an anchor point to a specific commit that does not change. And the changes are synchronized to the GitHub repository. ![]() It is important to remember that the synchronization between the GerritHub and GitHub repository done in one way.Īll the patches, tags and merges are done in front of the GerritHub system. The system integrates with the GitHub repository and accepts patches for the review. In our projects, we are using a GerritHub code review system. The following article will show the steps that should be accomplished in order to tag a new version in gerrit. Semantic versioning is a common template that guides us on how to tag a new version. This will help users to understand what are the changes that have been merged and give the ability to switch to the earlier version of the release in case of issues. C CS225 Project ID: 10990615 Star 0 0 Commits 1 Branch 0 Tags 0 Bytes Project Storage. When a new set of changes merged into the working branch, you would like to tag it with a specific version. This can be done with two commands: git fetch release git merge. ![]()
0 Comments
Leave a Reply. |