This guide is still under development Trevor Bramwell
The first step is to create a Gitlab account. You'll need to have verify your account with a credit card before CI jobs can be ran in your personal or project forks.
Gitlab Branch Workflow
- Clone the project
- edit, git add, commit
Write you change (remember to include `-s` to sign off commits: `git
commit -s`) - git push
- Click the link from the message to open a merge request to the
upstream repository - If you have multiple commits, write a detailed explanation about what you're asking to be merged in.
Set the change to "Draft" if its still being worked on. - Wait for CI to pass and a CODEOWNER to review.
If the project is utilizing hardware for their CI, a developer will need to approve your pipeline to run before it is tested.
Gitlab Fork Workflow
- Fork the project
- Setup mirroring
Alternatively manage this yourself by adding an extra 'upstream'
remote and routinely 'git pull upstream/master','git push origin master' - Clone your fork
- Checkout a new branch to make your change
- edit, git add, commit
Write you change (remember to include `-s` to sign off commits: `git
commit -s`) - git push
- Click the link from the message to open a merge request to the
upstream repository
Make sure the source branch comes from your fork and the target is the upstream repository - If you have multiple commits, write a detailed explanation about what you're asking to be merged in.
Set the change to "Draft" if its still being worked on. - Wait for CI to pass and a CODEOWNER to review.
If the project is utilizing hardware for their CI, a developer will need to approve your pipeline to run before it is tested.