From 2bf444c36495cb0173748e639b3f5bb743394c66 Mon Sep 17 00:00:00 2001 From: Alexey Igrychev Date: Wed, 10 Mar 2021 16:12:57 +0000 Subject: [PATCH 1/2] [readme] Remove broken link --- README.md | 2 +- build/README.md | 2 +- cleanup/README.md | 2 +- converge/README.md | 2 +- dismiss/README.md | 2 +- install/README.md | 2 +- run/README.md | 2 +- 7 files changed, 7 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index fc7dddc..bdf8782 100644 --- a/README.md +++ b/README.md @@ -33,7 +33,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.2 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.2 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 diff --git a/build/README.md b/build/README.md index 89c6a92..1e79a3d 100644 --- a/build/README.md +++ b/build/README.md @@ -9,7 +9,7 @@ The action combines all the necessary steps in itself and logic may be divided i ### werf binary setup -By default, all actions setup actual werf version for [1.2 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.2 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 diff --git a/cleanup/README.md b/cleanup/README.md index 1131982..8e222eb 100644 --- a/cleanup/README.md +++ b/cleanup/README.md @@ -9,7 +9,7 @@ The action combines all the necessary steps in itself and logic may be divided i ### werf binary setup -By default, all actions setup actual werf version for [1.2 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.2 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 diff --git a/converge/README.md b/converge/README.md index 10aca43..e6bb48b 100644 --- a/converge/README.md +++ b/converge/README.md @@ -9,7 +9,7 @@ The action combines all the necessary steps in itself and logic may be divided i ### werf binary setup -By default, all actions setup actual werf version for [1.2 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.2 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 diff --git a/dismiss/README.md b/dismiss/README.md index d40c70c..331fa60 100644 --- a/dismiss/README.md +++ b/dismiss/README.md @@ -9,7 +9,7 @@ The action combines all the necessary steps in itself and logic may be divided i ### werf binary setup -By default, all actions setup actual werf version for [1.2 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.2 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 diff --git a/install/README.md b/install/README.md index 03bb7e1..a631598 100644 --- a/install/README.md +++ b/install/README.md @@ -3,7 +3,7 @@

___ -By default, all actions setup actual werf version for [1.2 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.2 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 diff --git a/run/README.md b/run/README.md index 3ddae6b..8c2b246 100644 --- a/run/README.md +++ b/run/README.md @@ -9,7 +9,7 @@ The action combines all the necessary steps in itself and logic may be divided i ### werf binary setup -By default, all actions setup actual werf version for [1.2 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.2 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 From 8f134231c24d33dd44d855fdbaedd82fd9a6b6cc Mon Sep 17 00:00:00 2001 From: Alexey Igrychev Date: Wed, 10 Mar 2021 16:16:10 +0000 Subject: [PATCH 2/2] [readme] Update links to werf documentation --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index bdf8782..6af463a 100644 --- a/README.md +++ b/README.md @@ -13,7 +13,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.2-alpha/documentation/advanced/ci_cd/github_actions.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 @@ -97,7 +97,7 @@ If necessary, the user can define an arbitrary container registry using the `WER WERF_REPO_CONTAINER_REGISTRY: "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.2-alpha/documentation/advanced/supported_container_registries.html). ## Examples