Skip to content

Docs: (EE Port) Fixing anchors and links for all docs related to issues.

Marcel Amirault requested to merge (removed):docs-anchors7-issues-ee into master

What does this MR do?

This is the EE Port of https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/25516, which fixes all anchors that are related to issues, and also touches a few minor copy-edit issues that were in the same line or section as the anchor fixes, including changing some links to relative links.

Additional EE-Only issues anchors were fixed, as well as a few minor copy edits in the related sections (punctuation, redirect, relative links, etc...)

This is continuing the effort to clean up all the broken links project-wide (https://gitlab.com/gitlab-com/gitlab-docs/issues/330).

Related issues

https://gitlab.com/gitlab-com/gitlab-docs/issues/330

Author's checklist

  • Follow the Documentation Guidelines and Style Guide.
  • 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

  1. Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
  2. Ensure a release milestone is set and that you merge the equivalent EE MR before the CE MR if both exist.
  3. If there has not been a technical writer review, create an issue for one using the Doc Review template.
Edited by 🤖 GitLab Bot 🤖

Merge request reports