From f2f3f90f94a032833705023980f5940eeb46e98a Mon Sep 17 00:00:00 2001 From: Stefan Bueringer Date: Wed, 27 Apr 2022 16:51:17 +0200 Subject: [PATCH] book: fix link to GitHub doc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Stefan Büringer buringerst@vmware.com --- docs/book/src/clusterctl/provider-contract.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/book/src/clusterctl/provider-contract.md b/docs/book/src/clusterctl/provider-contract.md index b95c38c655bb..572c219cf21a 100644 --- a/docs/book/src/clusterctl/provider-contract.md +++ b/docs/book/src/clusterctl/provider-contract.md @@ -46,7 +46,7 @@ A GitHub release can be used as a provider repository if: * The release tag is a valid semantic version number * The components YAML, the metadata YAML and eventually the workload cluster templates are include into the release assets. -See the [GitHub help](https://help.github.com/en/github/administering-a-repository/creating-releases) for more information +See the [GitHub help](https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository) for more information about how to create a release. #### Creating a local provider repository