aboutsummaryrefslogtreecommitdiffstats
path: root/builds.sr.ht/triggers.md
diff options
context:
space:
mode:
authorDrew DeVault <sir@cmpwn.com>2018-11-08 09:59:50 -0500
committerDrew DeVault <sir@cmpwn.com>2018-11-08 09:59:50 -0500
commitc901e4f0bc67d56e5fe10e4ef365306202cf7978 (patch)
treefa72e74afadf0b19ee7d5f79654926a2a8c8caf2 /builds.sr.ht/triggers.md
parentbac8b48b11a99acb695371d7a146cc46336d237f (diff)
downloadsr.ht-docs-c901e4f0bc67d56e5fe10e4ef365306202cf7978.tar.gz
Include YAML example on triggers.md
Diffstat (limited to 'builds.sr.ht/triggers.md')
-rw-r--r--builds.sr.ht/triggers.md9
1 files changed, 8 insertions, 1 deletions
diff --git a/builds.sr.ht/triggers.md b/builds.sr.ht/triggers.md
index 2b00e70..2f20d79 100644
--- a/builds.sr.ht/triggers.md
+++ b/builds.sr.ht/triggers.md
@@ -1,5 +1,5 @@
At the end of a job or a job group, you can execute triggers based on the
-outcome of the job. The basic format is (in YAML or JSON):
+outcome of the job. The basic format is (in JSON):
{
"action": "trigger type",
@@ -7,6 +7,13 @@ outcome of the job. The basic format is (in YAML or JSON):
[...action-specific configuration...]
}
+Or in YAML:
+
+ triggers:
+ - action: trigger type
+ condition: when to execute this trigger
+ ...action-specific configuration...
+
Condition may be one of the following:
- **always**: execute the trigger after every build