Update all backend instances of old docs testing URL
What does this MR do?
This MR handles the backend changes related to splitting apart a page in !145054 (merged):
- Old: https://docs.gitlab.com/ee/development/documentation/testing.html
- New: https://docs.gitlab.com/ee/development/documentation/testing/
The docs-centric changes were handled in the initial MR. For the related updates in other repos, see the other MRs linked to #442483 (closed).
Files changed
.gitlab/issue_templates/Doc_cleanup.md
doc/.vale/gitlab/ReadingLevel.yml
doc/.vale/gitlab/Uppercase.yml
doc/api/graphql/reference/index.md
doc/index.md
lefthook.yml
scripts/lint/check_mermaid.mjs
tooling/graphql/docs/helper.rb
tooling/graphql/docs/templates/default.md.haml
Related issues
Related to Track splitting docs testing page apart (#442483 - closed)
Author's checklist
-
Optional. Consider taking the GitLab Technical Writing Fundamentals course. -
Follow the: -
If you're adding a new page, add the product tier badge under the H1 topic title. -
If you are a GitLab team member, request a review based on: - The documentation page's metadata.
- The associated Technical Writer.
If you are a GitLab team member and only adding documentation, do not add any of the following labels:
~"frontend"
~"backend"
~"type::bug"
~"database"
These labels cause the MR to be added to code verification QA issues.
Reviewer's checklist
Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.
If you aren't sure which tech writer to ask, use roulette or ask in the #docs Slack channel.
-
If the content requires it, ensure the information is reviewed by a subject matter expert. - Technical writer review items:
-
Ensure docs metadata is present and up-to-date. -
Ensure the appropriate labels are added to this MR. -
Ensure a release milestone is set. - If relevant to this MR, ensure content topic type principles are in use, including:
-
The headings should be something you'd do a Google search for. Instead of Default behavior
, say something likeDefault behavior when you close an issue
. -
The headings (other than the page title) should be active. Instead of Configuring GDK
, say something likeConfigure GDK
. -
Any task steps should be written as a numbered list. - If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
-
-
-
Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review.
Edited by Amy Qualls