When contributing to the GitLab Handbook you might run into situations that requires some further support to resolve. The sections below cover common scenarios that team members run into and provides information on how to deal with it.
In the GitLab Unfiltered video above, two colleagues share their screens and walk through the process detailed below.
If you create a merge request during a period where there is an issue in master causing pipelines to fail, you'll notice that failures will continue to occur even if you retry pipeline within the GitLab Web IDE interface.
Once the issue in master is fixed, you can solve this by using terminal to merge the latest version of master into your branch (which you can find in your merge request).
For those who primarily use Web IDE to interface with GitLab, it can feel foreign to engage locally. Before diving in deeper, be sure to read our GitLab 101 – a primer for the non-technical blog post.
The process is fairly straightforward once you have completed the necessary steps listed in the GitLab Handbook to edit locally.
Once you are properly equipped to edit locally, open a terminal window and execute the following.
git checkout master
git pull(This brings in the most recent changes from master to your local machine.)
git checkout MYBRANCH(Replace
MYBRANCHwith your branch from the merge request. This is easily copied by clicking the Copy Branch Name icon to the right of Request to merge at the top of your merge request page.)
git merge master(This takes the changes from master and merges them into your local
:qfollowed by a Return keystroke quits vim which is the editor your terminal opened when adding the stock commit message to the merge.)
git push(This takes local machine files and pushes to the cloud.)
Once this has been executed, you'll see new commits added to your merge request, and the pipeline will automatically begin to re-run. If completed correctly, the pipeline will pass now that the latest master was merged into your branch.
If you are a GitLab team member and you get stuck, please ask for help in the
#mr-buddies Slack channel.
In the GitLab Unfiltered video above, Jean shares a quick overview of how to go about identifying why a pipeline might be failing for a merge request to the GitLab handbook.
If you've made a merge request, only to see that your pipeline has failed, a troubleshooting process begins.
You can learn more about why pipelines fail, what failures mean, and how to resolve conflicts by viewing this explainer video hosted on GitLab Unfiltered.
For those inside the GitLab organization, you can request help on individual merge requests via Merge Request Buddies in the
#mr-buddies Slack channel.
If you suspect a systemic issue, inquire in the
#handbook-escalation Slack channel, and check to see if others are reporting similar errors in
#is-this-known. For more information refer to the Handbook On-Call page.
#handbook-escalation Slack channel is used for monitoring and responding to infrastructure and configuration related build issues with the
www-gitlab-com project master branch. This is an excellent first stop to see if there is an ongoing issue impacting your pipeline.
The Static Site Editor Team is responsible for enhancing the editing experience for static sites inside of GitLab, including the handbook.
General GitLab handbook discussion occurs in the
#handbook channel, while an automated feed of merged handbook updates can be found in the
To the ensure consistency, quality and correctness of the GitLab Handbook we use various linting jobs that run as part of the pipeline. These jobs check that everything is as it should be, and if they detect something is wrong will cause the pipeline to fail.
There is a special linter that validates links and anchors across the handbook. If your change accidentally breaks a link, then the pipeline job will fail with a similar error message.
sites/handbook/source/handbook/total-rewards/benefits/general-and-entity-benefits/pty-benefits-australia/index.html.md, line number: 87)
expense-reimbursementis defined in the file path from step 1 but does not exist in the file path from step 3.
Expense Reimbursementneeds to be defined. (file path -
How to fix the problem
Double-check that header
Expense Reimbursement exists in
If it was moved or renamed, then update the link with the anchor to point to the correct location.