From 9433c739e34cda052bcabc05619021e16ee91762 Mon Sep 17 00:00:00 2001
From: lonix1 <40320097+lonix1@users.noreply.github.com>
Date: Wed, 13 Sep 2023 15:21:13 +0200
Subject: [PATCH] docs: missing info for runs_on (#2457)

The `runs_on` section is missing from the syntax docs. So I added a
section for it, and linked to an example.

It's good enough. But I think it might be a good idea for someone (with
more knowledge than me) to add more info in this section. How to use it,
when to use it, etc. The example is useful but not very informative.
---
 docs/docs/20-usage/20-pipeline-syntax.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/docs/docs/20-usage/20-pipeline-syntax.md b/docs/docs/20-usage/20-pipeline-syntax.md
index bd44e18e1..c890e34c6 100644
--- a/docs/docs/20-usage/20-pipeline-syntax.md
+++ b/docs/docs/20-usage/20-pipeline-syntax.md
@@ -887,6 +887,10 @@ when:
 
 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.
 
+## `runs_on`
+
+Workflows that should run even on failure should set the `runs_on` tag. See [here](./25-workflows.md#flow-control) for an example.
+
 ## Privileged mode
 
 Woodpecker gives the ability to configure privileged mode in the YAML. You can use this parameter to launch containers with escalated capabilities.