Introduction How-To

Note

Before reading this document, please be sure that you have fully read and understood the Git&Gitlab Workflow introduction and presentation

This document will present the different procedures that will be applied for the new GIT workflow. The GIT workflow has been presented in detail in the documentation file named GIT&GitLab Documentation that can be found in the PLMTF Share Point. Please be sure to have read and fully understood the GIT workflow documentation report before applying the procedures presented in this document.

Through the following “How-To”, different GIT terms will be used. These terms are presented in this list followed by the Figure 13

  • Upstream: The upstream repository is the main repository that will be visible for final users. This repository is public to the users that are logged-in in the GitLab server. However, only the user with the Master privileges will be able to modify it directly. In this case, this is the repository that contains the branches “master”, “dev” and “dev”.
  • Fork: Forked repositories are clones (on the server) of the entire upstream repository. The users who fork the master repository will see themselves granted the Master role in their forked repository. Changes made in the forked repositories won’t be retrieved by the upstream repository.
  • Local repository: Local copy of a repository. For this scenario, users will only have a local copy of the fork repository.
  • Origin: In a local repository perspective, the Origin repository will be the server repository that has been cloned. In this case, Origin will refer to the forked repository.
  • Project: GitLab term that references a GIT repository.
  • Checkout: Process to switch from one branch to another.
_images/image.png

Figure 13 Workflow representation