From 6ab9f802d1db318203c95e468398a252d438c472 Mon Sep 17 00:00:00 2001 From: 6543 <6543@obermui.de> Date: Tue, 13 Jun 2023 18:58:26 +0200 Subject: [PATCH] Fix links in docs (#1859) --- docs/docs/20-usage/20-pipeline-syntax.md | 2 +- .../version-0.15/20-usage/25-multi-pipeline.md | 5 +++-- .../version-0.15/30-administration/10-server-config.md | 2 +- 3 files changed, 5 insertions(+), 4 deletions(-) diff --git a/docs/docs/20-usage/20-pipeline-syntax.md b/docs/docs/20-usage/20-pipeline-syntax.md index 80585c36b..6d908044e 100644 --- a/docs/docs/20-usage/20-pipeline-syntax.md +++ b/docs/docs/20-usage/20-pipeline-syntax.md @@ -887,7 +887,7 @@ when: ## `depends_on` -Woodpecker supports to define multiple workflows for a repository. Those workflows will run independent from each other. To depend them on each other you can use the [`depends_on`](https://woodpecker-ci.org/docs/usage/workflows#flow-control) keyword. +Woodpecker supports to define multiple workflows for a repository. Those workflows will run independent from each other. To depend them on each other you can use the [`depends_on`](./25-workflows.md#flow-control) keyword. ## Privileged mode diff --git a/docs/versioned_docs/version-0.15/20-usage/25-multi-pipeline.md b/docs/versioned_docs/version-0.15/20-usage/25-multi-pipeline.md index 5ddaea23f..15b93659e 100644 --- a/docs/versioned_docs/version-0.15/20-usage/25-multi-pipeline.md +++ b/docs/versioned_docs/version-0.15/20-usage/25-multi-pipeline.md @@ -6,7 +6,7 @@ This Feature is only available for GitHub, Gitea & GitLab repositories. Follow [ By default, Woodpecker looks for the pipeline definition in `.woodpecker.yml` in the project root. -The Multi-Pipeline feature allows the pipeline to be split into several files and placed in the `.woodpecker/` folder. Only `.yml` files will be used and files in any subfolders like `.woodpecker/sub-folder/test.yml` will be ignored. You can set some custom path like `.my-ci/pipelines/` instead of `.woodpecker/` in the [project settings](./71-project-settings.md). +The Multi-Pipeline feature allows the pipeline to be split into several files and placed in the `.woodpecker/` folder. Only `.yml` files will be used and files in any subfolders like `.woodpecker/sub-folder/test.yml` will be ignored. You can set some custom path like `.my-ci/pipelines/` instead of `.woodpecker/` in the [project settings](./71-project-settings.md). ## Rational @@ -15,9 +15,10 @@ The Multi-Pipeline feature allows the pipeline to be split into several files an - utilizing more agents to speed up build ## Example multi-pipeline definition + :::warning Please note that files are only shared between steps of the same pipeline (see [File changes are incremental](./20-pipeline-syntax.md#file-changes-are-incremental)). That means you cannot access artifacts e.g. from the `build` pipeline below in the `deploy` pipeline. -If you still need to pass artifacts between the pipelines you need use storage [plugins](docs/usage/plugins/plugins) (e.g. one which stores files in an Amazon S3 bucket). +If you still need to pass artifacts between the pipelines you need use storage [plugins](./51-plugins/10-plugins.md) (e.g. one which stores files in an Amazon S3 bucket). ::: ```bash diff --git a/docs/versioned_docs/version-0.15/30-administration/10-server-config.md b/docs/versioned_docs/version-0.15/30-administration/10-server-config.md index 9154c625b..f00278993 100644 --- a/docs/versioned_docs/version-0.15/30-administration/10-server-config.md +++ b/docs/versioned_docs/version-0.15/30-administration/10-server-config.md @@ -4,7 +4,7 @@ Registration is closed by default. While disabled an administrator needs to add new users manually (exp. `woodpecker-cli user add`). -If registration is open every user with an account at the configured [SCM](docs/administration/vcs/overview) can login to Woodpecker. +If registration is open every user with an account at the configured [SCM](./11-vcs/10-overview.md) can login to Woodpecker. This example enables open registration for users that are members of approved organizations: ```diff