From 8413bb06209d056fc0cdea32c2e0b2054152e077 Mon Sep 17 00:00:00 2001 From: Nulo <86896666+catdevnull@users.noreply.github.com> Date: Sun, 19 Sep 2021 08:02:24 -0300 Subject: [PATCH] Remove non-existent changed status condition from docs (#322) * docs(status): rewrite status: changed doesn't exist in the current codebase and the description was just confusing. * Use consistent language Co-authored-by: Anbraten Co-authored-by: Nulo Co-authored-by: Anbraten --- docs/docs/20-usage/20-pipeline-syntax.md | 13 +------------ 1 file changed, 1 insertion(+), 12 deletions(-) diff --git a/docs/docs/20-usage/20-pipeline-syntax.md b/docs/docs/20-usage/20-pipeline-syntax.md index e45ba7a80..68c385a50 100644 --- a/docs/docs/20-usage/20-pipeline-syntax.md +++ b/docs/docs/20-usage/20-pipeline-syntax.md @@ -243,18 +243,7 @@ when: ### `status` -Execute a step when the build status changes: - -```diff -when: - status: changed -``` - -Woodpecker uses the container exit code to determine the success or failure status of a build. Non-zero exit codes fail the build and cause the pipeline to immediately exit. - -There are use cases for executing pipeline steps on failure, such as sending notifications for failed builds. Use the status constraint to override the default behavior and execute steps even when the build status is failure: - -Execute a step when the build is passing or failing: +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: ```diff pipeline: