From 069d6e4929e9b91e8a51114887797d338d36411c Mon Sep 17 00:00:00 2001 From: Evan Read Date: Mon, 18 Jul 2022 10:48:56 +1000 Subject: Fix invalid anchor links --- doc/maintenance.md | 4 ++-- doc/releases.md | 4 +--- 2 files changed, 3 insertions(+), 5 deletions(-) (limited to 'doc') diff --git a/doc/maintenance.md b/doc/maintenance.md index ef8636a7..6d993b8e 100644 --- a/doc/maintenance.md +++ b/doc/maintenance.md @@ -4,9 +4,9 @@ Some of the issues that the GitLab technical writing team handles to maintain include: - The [deployment process](#deployment-process). -- [Algolia search](#algolia-search). +- [Algolia search](docsearch.md). - Temporary [event or survey banners](#survey-banner). -- [CSP headers](#csp-header) +- [CSP headers](#csp-header). ## Deployment process diff --git a/doc/releases.md b/doc/releases.md index 5d49de5d..df581220 100644 --- a/doc/releases.md +++ b/doc/releases.md @@ -163,7 +163,6 @@ The merge requests for the dropdowns should now all be merged into their respect 1. Check the [pipelines page](https://gitlab.com/gitlab-org/gitlab-docs/pipelines) and make sure the pipelines in all the MRs are green. -1. Merge all of the [dropdown merge requests](#update-dropdown-for-online-versions). 1. Merge the [release merge request](#create-release-merge-request). 1. Each merge triggers a new pipeline for each stable branch. Check the [pipelines page](https://gitlab.com/gitlab-org/gitlab-docs/-/pipelines) and wait @@ -187,8 +186,7 @@ For example, if you released the 14.1 documentation, the first dropdown entry sh ### `Could not find remote branch` error -When you create the [stable branch](#create-stable-branch-and-docker-image-for-release) -or create the MRs to [update the dropdown](#update-dropdown-for-online-versions), +When you create the [stable branch](#create-stable-branch-and-docker-image-for-release), the pipeline fails with an error similar to the following: ```shell -- cgit v1.2.3