Skip to content

Commit

Permalink
book: fix link to GitHub doc
Browse files Browse the repository at this point in the history
Signed-off-by: Stefan Büringer [email protected]
  • Loading branch information
sbueringer committed Apr 27, 2022
1 parent 3bff7da commit e2f8a04
Show file tree
Hide file tree
Showing 2 changed files with 9 additions and 4 deletions.
11 changes: 8 additions & 3 deletions .markdownlinkcheck.json
Original file line number Diff line number Diff line change
@@ -1,9 +1,14 @@
{
"ignorePatterns": [
{
"ignorePatterns": [{
"pattern": "^http://localhost"
}],
"httpHeaders": [{
"comment": "Workaround as suggested here: https://github.com/tcort/markdown-link-check/issues/201",
"urls": ["https://docs.github.com/"],
"headers": {
"Accept-Encoding": "zstd, br, gzip, deflate"
}
],
}],
"timeout": "5s",
"retryOn429": true,
"retryCount": 5,
Expand Down
2 changes: 1 addition & 1 deletion docs/book/src/clusterctl/provider-contract.md
Original file line number Diff line number Diff line change
Expand Up @@ -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 docs](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
Expand Down

0 comments on commit e2f8a04

Please sign in to comment.