GIT-LAB
- Gitlab is
- A DevOps Platform delivered as a single application
- Provides access to Git Repositories c. Provides source code management
- Developers can to:
- Collaborate
- Work from a local copy
- Branch and merge code
- Streamline testing and delivery with CI/CD
Branches
- Branches stores all files in GitLab
- The master branch stores the deployable code
- Create a new branch for planned changes
Merging Branches
- Both start with the common code base
- When new features are developed both codes are merged with the tip to a newly merged commit
Commit
- Git commits are one of the key parts of a Git repository, the commit message is a lifelog for the repository.
- As the project/repository evolves over time (new features getting added, bugs being fixed), commit messages are the place where one can see what was changed and how.
Pull Request
- A pull request makes the proposed changes available for others to review and use.
- A pull can follow any commits, even if the code is unfinished
- GitLab automatically indicates to pull the request.
- Log files record the approval of the merge
Pull Request
- The Master branch should be the only deployed code.
- Developers can change source files in a branch but the changes are not released until
- They are committed
- A pull command is issued
- Then the code is merged into the master code.
Clone
- Git Clone is used to clone the project into local
- Syntax
- git clone {repository URL}
Should you have any questions/suggestions, please feel free to comment below. I will do my best to get back. Looking forward to hearing from you!