Skip to content

Commit 27d2429

Browse files
authored
Fix README.md links (#267)
1 parent 9a31fda commit 27d2429

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -147,7 +147,7 @@ This project uses [Semantic Versioning](https://semver.org/) and its version is
147147
automatically determined by [release-drafter](https://github.com/release-drafter/release-drafter)
148148
based on the labels of the pull requests merged into the `main` branch.
149149

150-
See the [release-drafter configuration](../.github/release-drafter.yml) for more details.
150+
See the [release-drafter configuration](./.github/release-drafter.yml) for more details.
151151

152152
## Creating a New Release
153153

@@ -157,9 +157,9 @@ create a draft release or update the existing draft release in the [Releases](ht
157157
To create a new release you need to publish the existing draft release created by release-drafter.
158158

159159
> [!IMPORTANT]
160-
> Make sure the [release-drafter workflow](../.github/workflows/release-drafter.yml) is finished before publishing the release.
160+
> Make sure the [release-drafter workflow](https://github.com/elastic/docs-builder/actions/workflows/release-drafter.yml) is finished before publishing the release.
161161

162162
> [!NOTE]
163-
> When a release is published, the [create-major-tag workflow](../.github/workflows/create-major-tag.yml)
163+
> When a release is published, the [create-major-tag workflow](./.github/workflows/create-major-tag.yml)
164164
> will force push a new major tag in the format `vX` where `X` is the major version of the release.
165165
> For example, if the release is `1.2.3` was published, the workflow will force push a new tag `v1` on the same commit.

0 commit comments

Comments
 (0)