Update the route map for hugo-based docs site
What does this MR do and why?
As per the related issue, we need to update the route map for review apps to point to the correct URL path. To be merged as part of the rollout.
References
Resolves gitlab-org/technical-writing/docs-gitlab-com#195 (closed)
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
Merge request reports
Activity
changed milestone to %17.9
added Technical Writing maintenancerefactor typemaintenance labels
requested review from @sarahgerman
assigned to @marcel.amirault
added pipelinetier-1 label
1 Message This merge request adds or changes documentation files and requires Technical Writing review. The review should happen before merge, but can be post-merge if the merge request is time sensitive. Documentation review
The following files require a review from a technical writer:
-
doc/ci/cloud_deployment/_index.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
DangerEdited by ****-
added documentation label
- Resolved by Sarah German
@sarahgerman I think this does the trick? Works already for
_index.md
, though I think we should wait until rollout to merge for the second rule to work properly. WDYT?
- Resolved by Sarah German
added pipeline:mr-approved label
added pipelinetier-2 label and removed pipelinetier-1 label
Before you set this MR to auto-merge
This merge request will progress on pipeline tiers until it reaches the last tier: pipelinetier-3. We will trigger a new pipeline for each transition to a higher tier.
Before you set this MR to auto-merge, please check the following:
- You are the last maintainer of this merge request
- The latest pipeline for this merge request is pipelinetier-3 (You can find which tier it is in the pipeline name)
- This pipeline is recent enough (created in the last 8 hours)
If all the criteria above apply, please set auto-merge for this merge request.
See pipeline tiers and merging a merge request for more details.
mentioned in issue gitlab-org/technical-writing/docs-gitlab-com#164 (closed)
changed milestone to %17.10
added missed:17.9 label
requested review from @axil
- Resolved by Michael Belton
@axil Can you merge this one?
requested review from @eread
- Resolved by Michael Belton
@marcel.amirault Did you want to port this to the other docs projects?
added pipelinetier-3 label and removed pipelinetier-2 label
requested review from @michael.belton
started a merge train
mentioned in commit d4886985
added workflowstaging-canary label
mentioned in merge request gitlab-runner!5365 (merged)
mentioned in merge request omnibus-gitlab!8183 (merged)
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 workflowpost-deploy-db-production label and removed workflowpost-deploy-db-staging label
added releasedpublished label