Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitlab-docs.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFiona Neill <fneill@gitlab.com>2022-09-26 11:36:04 +0300
committerFiona Neill <fneill@gitlab.com>2022-09-26 11:36:04 +0300
commit149c9db55d1f684ac209f70cd8b5211bb23a11bf (patch)
tree17d9a3a6305628df3037553deb30250328c61bea
parent1fb690f9d2b59dc3242e66f3cc17b0bc2113ab68 (diff)
parentb90e3b57e97d9fcdf799e8fe5c2957dbd7d8513f (diff)
Merge branch 'kpaizee-main-patch-63683' into 'main'
Fix instructions for merging release MR See merge request https://gitlab.com/gitlab-org/gitlab-docs/-/merge_requests/3122 Merged-by: Fiona Neill <fneill@gitlab.com> Co-authored-by: Kati Paizee <kpaizee@gitlab.com>
-rw-r--r--.gitlab/issue_templates/release.md3
1 files changed, 2 insertions, 1 deletions
diff --git a/.gitlab/issue_templates/release.md b/.gitlab/issue_templates/release.md
index c2c00b03..133dfbd9 100644
--- a/.gitlab/issue_templates/release.md
+++ b/.gitlab/issue_templates/release.md
@@ -30,11 +30,12 @@ After release post is live on the 22nd, or the next Monday morning if the releas
has passed and created a [Docker image](https://gitlab.com/gitlab-org/gitlab-docs/container_registry/631635?orderBy=NAME&sort=desc&search[]=)
tagged the release version. ([If it fails, how do I fix it?](https://gitlab.com/gitlab-org/gitlab-docs/-/blob/main/doc/releases.md#imagedocs-latest-job-fails-due-to-broken-links))
1. Deploy the versions:
+ 1. [ ] Merge the docs release merge request.
1. [ ] Go to the [scheduled pipelines page](https://gitlab.com/gitlab-org/gitlab-docs/-/pipeline_schedules)
and run the `Build Docker images weekly` pipeline.
1. [ ] In the scheduled pipeline you just started, cancel the pipeline, and manually run the `image:docs-latest`
job that builds the `:latest` Docker image.
- 1. [ ] When the job is complete, merge the docs release merge request.
+ 1. [ ] When the job is complete, run the `Build docs.gitlab.com every hour` scheduled pipeline.
1. [ ] After the deployment completes, open `docs.gitlab.com` in a browser. Confirm
both the latest version and the correct pre-release version are listed in the documentation version dropdown.
1. [ ] Check all published versions of the docs to ensure they are visible and that their version menus have the latest versions.