From d1912cdef20b8817b66f865f8b514afad015c32c Mon Sep 17 00:00:00 2001 From: Jeppe Reinhold Date: Tue, 27 Jun 2023 01:32:15 +0200 Subject: [PATCH] add note about starting CI, see #23198 --- CONTRIBUTING/RELEASING.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING/RELEASING.md b/CONTRIBUTING/RELEASING.md index 120d834f839a..5a999af5e6de 100644 --- a/CONTRIBUTING/RELEASING.md +++ b/CONTRIBUTING/RELEASING.md @@ -13,7 +13,7 @@ - [Publishing](#publishing) - [👉 How to Release](#-how-to-release) - [1. Find the Prepared Pull Request](#1-find-the-prepared-pull-request) - - [2. Freeze the Pull Request](#2-freeze-the-pull-request) + - [2. Freeze the Pull Request and run CI](#2-freeze-the-pull-request-and-run-ci) - [3. QA Each Merged Pull Request](#3-qa-each-merged-pull-request) - [4. Re-trigger the Workflow](#4-re-trigger-the-workflow) - [5. Make Manual Changes](#5-make-manual-changes) @@ -247,12 +247,14 @@ Look for the release pull request that has been prepared for the type of release For example: https://github.com/storybookjs/storybook/pull/23148 -### 2. Freeze the Pull Request +### 2. Freeze the Pull Request and run CI Add the "**freeze**" label to the pull request. This will stop the preparation workflows from running when new changes to `next` are merged. This allows you to make changes without worrying about other people's work overriding yours. The "**freeze**" label does not cancel the workflows when they are triggered manually, so you can still run the workflow. +You also need to add the "**ci:daily**" label to the pull request to trigger CI runs. This will start a full CI run and re-run on any changes. CI does not run by default to avoid unnecessary re-runs until a new release is being created. + ### 3. QA Each Merged Pull Request It is important to verify that the release includes the right content. Key elements to account for are: