Update links to MRs in the docs (to use hyphens)
What does this MR do?
The paths to MRs now have hyphens, so all docs linking to MRs need to have hyphens added to avoid unnecessary redirects. I did a find and replace for all MRs to update them. The commands I used was (I went extra details on the find/replace to make sure I didn't catch anything that shouldn't be updated):
grep -rl 'gitlab-org\/gitlab\/merge_requests' . | xargs sed -i '' -e 's/gitlab- org\/gitlab\/merge_requests/gitlab-org\/gitlab\/-\/merge_requests/g'grep -rl 'gitlab-org\/gitlab-foss\/merge_requests' . | xargs sed -i '' -e 's/gi tlab-org\/gitlab-foss\/merge_requests/gitlab-org\/gitlab-foss\/-\/merge_requests/g'- (Same for Runner, Omnibus, Charts)
- A few were done by hand, check the commit list.
Related issues
Related to gitlab-docs#601 (closed)
Author's checklist
-
Follow the Documentation Guidelines and Style Guide. -
If applicable, update the permissions table. -
Link docs to and from the higher-level index page, plus other related docs where helpful. -
Apply the documentation label.
Review checklist
All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.
1. Primary Reviewer
-
Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.
2. Technical Writer
-
Optional: Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage.
3. Maintainer
-
Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review. -
Ensure a release milestone is set. -
If there has not been a technical writer review, create an issue for one using the Doc Review template.
Edited by 🤖 GitLab Bot 🤖