self-hosted/woodpecker
1
0
Fork 0
mirror of https://github.com/woodpecker-ci/woodpecker.git synced 2025-01-17 17:45:03 +02:00
Code Issues Releases Activity

[Docs] Remove never implemented "tag"-filter and document "ref"-filter to do the same (#1820)

Browse Source 
close #1211
This commit is contained in:
6543 2023-06-04 12:13:32 +02:00 committed by GitHub
parent 79c8da2f32
commit c919f32e0b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 4 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/docs/20-usage/20-pipeline-syntax.md
View File

@ -829,15 +829,15 @@ when:
event: [push, pull_request, tag, deployment] event: [push, pull_request, tag, deployment]
``` ```
### `tag` ### `ref`
This filter only applies to tag events. The `ref` filter compares the git reference against which the pipeline is executed.
Use glob expression to execute a step if the tag name starts with `v`: This allows you to filter, for example, tags that must start with **v**:
```diff ```diff
when: when:
event: tag event: tag
tag: v* ref: refs/tags/v*
``` ```
### `environment` ### `environment`

9
docs/versioned_docs/version-0.15/20-usage/22-conditional-execution.md
View File

@ -86,15 +86,6 @@ when:
event: [push, pull_request, tag, deployment] event: [push, pull_request, tag, deployment]
``` ```
## `tag`
Execute a step if the tag name starts with `release`:
```diff
when:
tag: release*
```
## `status` ## `status`
There are use cases for executing pipeline steps on failure, such as sending notifications for failed pipelines. Use the status constraint to execute steps even when the pipeline fails: There are use cases for executing pipeline steps on failure, such as sending notifications for failed pipelines. Use the status constraint to execute steps even when the pipeline fails: