Round 1: fix redirected / broken links
What does this MR do?
Begin fixing broken or redirected links in the docs.
Related issues
Related to technical-writing#1006
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.
Merge request reports
Activity
changed milestone to %16.10
added docsfix documentation maintenancerefactor tw-weight3 twdoing typemaintenance labels
assigned to @aqualls
I'll send this one to @jglassman1. Link fixes only.
requested review from @jglassman1
added Technical Writing label
added docs-only label
1 Message This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge. Documentation review
The following files require a review from a technical writer:
-
doc/administration/auth/ldap/ldap-troubleshooting.md
(Link to current live version) -
doc/administration/auth/oidc.md
(Link to current live version) -
doc/administration/dedicated/configure_instance.md
(Link to current live version) -
doc/administration/dedicated/create_instance.md
(Link to current live version) -
doc/administration/geo/replication/container_registry.md
(Link to current live version) -
doc/administration/geo/replication/single_sign_on.md
(Link to current live version) -
doc/administration/integration/diagrams_net.md
(Link to current live version) -
doc/administration/logs/index.md
(Link to current live version) -
doc/administration/monitoring/performance/performance_bar.md
(Link to current live version) -
doc/administration/incoming_email.md
(Link to current live version) -
doc/administration/nfs.md
(Link to current live version) -
doc/ci/yaml/index.md
(Link to current live version) -
doc/editor_extensions/jetbrains_ide/index.md
(Link to current live version) -
doc/gitlab-basics/start-using-git.md
(Link to current live version) -
doc/install/google_cloud_platform/index.md
(Link to current live version) -
doc/install/postgresql_extensions.md
(Link to current live version)
The review does not need to block merging this merge request. See the:
-
Metadata for the
*.md
files that you've changed. The first few lines of each*.md
file identify the stage and group most closely associated with your docs change. - The Technical Writer assigned for that stage and group.
- Documentation workflows for information on when to assign a merge request for review.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
Danger-
@jglassman1, did you forget to run a pipeline before you merged this work? Based on our code review process, if the latest pipeline was created more than 4 hours ago, you should:
- Ensure the merge request is not in Draft status.
- Start a pipeline (especially important for Community contribution merge requests).
- Set the merge request to auto-merge.
This is a guideline, not a rule. Please consider replying to this comment for transparency.
This message was generated automatically. You're welcome to improve it.
mentioned in commit d39cd758
added workflowstaging-canary label
added workflowcanary label and removed workflowstaging-canary label
added workflowstaging label and removed workflowcanary label
added workflowproduction label and removed workflowstaging label
added workflowpost-deploy-db-staging label and removed workflowproduction label
added releasedpublished label