From b48264c63a9dab719d8c1a04764a20751bcac0e1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Volkan=20O=CC=88zc=CC=A7elik?= Date: Tue, 19 Dec 2023 09:23:22 -0800 Subject: [PATCH] minor change MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Volkan Özçelik --- docs/_pages/0980-release-management.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/_pages/0980-release-management.md b/docs/_pages/0980-release-management.md index 9dd3413e..4967fd30 100644 --- a/docs/_pages/0980-release-management.md +++ b/docs/_pages/0980-release-management.md @@ -269,15 +269,15 @@ To start the release cycle, we initialize helm-charts for each official release of VSecM. Helm-charts are continuously developed and updated during the release development process. -At the beginning of a VSecM release, the [init-next-helm-chart.sh][init_script] +At the beginning of a VSecM release, the [./hack/init-next-helm-chart.sh][init_script] script is used to initialize the helm-charts. To initialize a new helm-chart, run the following command using the init script: -`./helm-charts/init_next_helm_chart.sh ` +`./hack/init_next_helm_chart.sh ` base-version: the existing helm-charts version to be used as the base helm-chart. new-version: the version helm-charts to be initialized. -For example: `./helm-charts/init_next_helm_chart.sh 0.21.0 0.22.0` +For example: `./hack/init_next_helm_chart.sh 0.21.0 0.22.0` After execution, the script will display a link on the console. Use this link to create a pull request (PR) and merge it into the main branch. @@ -318,7 +318,7 @@ folders. To add a snapshot of the current documentation: 1. Copy the `docs` folder into a temporary place like `/tmp/docs`. -2. Checkout the `gh-pages` branch. +2. Checkout the `docs` branch. 3. Copy the `docs` folder from `/tmp/docs` to the `gh-pages` branch: `cp -r /tmp/docs $WORKSPACE/secrets-manager/docs/`. 4. Update the `secrets-manager/docs//_includes/notification.html` file