From 27d2429fc1eb8a75db3c705a60e6424949c28d97 Mon Sep 17 00:00:00 2001 From: Jan Calanog Date: Mon, 20 Jan 2025 13:03:10 +0100 Subject: [PATCH] Fix README.md links (#267) --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 251969ac..b8be97d4 100644 --- a/README.md +++ b/README.md @@ -147,7 +147,7 @@ This project uses [Semantic Versioning](https://semver.org/) and its version is automatically determined by [release-drafter](https://github.com/release-drafter/release-drafter) based on the labels of the pull requests merged into the `main` branch. -See the [release-drafter configuration](../.github/release-drafter.yml) for more details. +See the [release-drafter configuration](./.github/release-drafter.yml) for more details. ## Creating a New Release @@ -157,9 +157,9 @@ create a draft release or update the existing draft release in the [Releases](ht To create a new release you need to publish the existing draft release created by release-drafter. > [!IMPORTANT] -> Make sure the [release-drafter workflow](../.github/workflows/release-drafter.yml) is finished before publishing the release. +> Make sure the [release-drafter workflow](https://github.com/elastic/docs-builder/actions/workflows/release-drafter.yml) is finished before publishing the release. > [!NOTE] -> When a release is published, the [create-major-tag workflow](../.github/workflows/create-major-tag.yml) +> When a release is published, the [create-major-tag workflow](./.github/workflows/create-major-tag.yml) > will force push a new major tag in the format `vX` where `X` is the major version of the release. > For example, if the release is `1.2.3` was published, the workflow will force push a new tag `v1` on the same commit.