From 4e62aa309eeb12892b98e4308e2ff0468a2b1969 Mon Sep 17 00:00:00 2001 From: Alexey Igrychev Date: Wed, 10 Mar 2021 16:20:24 +0000 Subject: [PATCH] [readme] Update links to werf documentation --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 0ad43ab..810ebc9 100644 --- a/README.md +++ b/README.md @@ -16,7 +16,7 @@ This action set allows you to organize CI/CD with GitHub Actions and [werf](http Each action combines all the necessary steps in itself and logic may be divided into environment setup and launching the corresponding command. -**Ready-to-use GitHub Actions Workflows** for different CI/CD workflows are available [here](https://werf.io/documentation/advanced/ci_cd/github_actions.html#complete-set-of-configurations-for-ready-made-workflows). +**Ready-to-use GitHub Actions Workflows** for different CI/CD workflows are available [here](https://werf.io/v1.1-alpha/documentation/guides/github_ci_cd_integration.html#complete-set-of-configurations-for-ready-made-workflows). > Also, there is another action — [werf/actions/install](https://github.com/werf/actions/tree/master/install). With this action a user can just install werf and use binary within job steps for own purposes @@ -36,7 +36,7 @@ When using actions, select the version corresponding to the `MAJOR.MINOR` versio ### werf binary setup -By default, all actions setup actual werf version for [1.1 alpha channel](https://werf.io/releases.html) (more details about channels, werf release cycle and compatibility promise [here](https://werf.io/installation.html#all-changes-in-werf-go-through-all-stability-channels)). +By default, all actions setup actual werf version for 1.1 alpha channel (more details about channels, werf release cycle and compatibility promise [here](https://werf.io/installation.html#all-changes-in-werf-go-through-all-stability-channels)). Using the `channel` input the user can switch the release channel. > This is recommended approach to be up-to-date and to use actual werf version without changing configurations @@ -102,7 +102,7 @@ If necessary, the user can define an arbitrary container registry using the `WER WERF_REPO_IMPLEMENTATION: "gcr" ``` -To learn how to work with the different container registries, see the corresponding [article in the werf documentation](https://werf.io/documentation/advanced/supported_container_registries.html). +To learn how to work with the different container registries, see the corresponding [article in the werf documentation](https://werf.io/v1.1-alpha/documentation/reference/working_with_docker_registries.html). ## Examples