aboutsummaryrefslogtreecommitdiffstats
path: root/builds.sr.ht/triggers.md
diff options
context:
space:
mode:
authorStephen Gregoratto <dev@sgregoratto.me>2019-01-14 14:04:59 +1100
committerDrew DeVault <sir@cmpwn.com>2019-01-14 07:53:30 -0500
commit7e055f2dd5256f0083ac446022ccc8328a5ad873 (patch)
tree8368e58653f7195df0a2988b4759350f058b176d /builds.sr.ht/triggers.md
parentd70774ecb1add3929d0c8491a8d7d7c9021e99da (diff)
downloadsr.ht-docs-7e055f2dd5256f0083ac446022ccc8328a5ad873.tar.gz
Use fenced code blocks where applicable.
Diffstat (limited to 'builds.sr.ht/triggers.md')
-rw-r--r--builds.sr.ht/triggers.md22
1 files changed, 13 insertions, 9 deletions
diff --git a/builds.sr.ht/triggers.md b/builds.sr.ht/triggers.md
index 45d47a9..50e040d 100644
--- a/builds.sr.ht/triggers.md
+++ b/builds.sr.ht/triggers.md
@@ -1,18 +1,22 @@
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 JSON):
- {
- "action": "trigger type",
- "condition": "when to execute this trigger",
- [...action-specific configuration...]
- }
+```
+{
+ "action": "trigger type",
+ "condition": "when to execute this trigger",
+ [...action-specific configuration...]
+}
+```
Or in YAML:
- triggers:
- - action: trigger type
- condition: when to execute this trigger
- ...action-specific configuration...
+```
+triggers:
+ - action: trigger type
+ condition: when to execute this trigger
+ ...action-specific configuration...
+```
Condition may be one of the following: