aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDrew DeVault <sir@cmpwn.com>2020-11-17 10:02:35 -0500
committerDrew DeVault <sir@cmpwn.com>2020-11-17 10:02:35 -0500
commit17cbf2be884ef065563b407fe6a40b2e6fb82ba4 (patch)
treeaeb344665075f841be84555aa3918c8c0669d79c
parentafa44235e24d863318a5a081cab3bf8e3f78ef3e (diff)
downloadsr.ht-docs-17cbf2be884ef065563b407fe6a40b2e6fb82ba4.tar.gz
Remove JSON from builds.sr.ht/triggers.md
This is no longer encouraged; machines can edit YAML.
-rw-r--r--builds.sr.ht/triggers.md16
1 files changed, 4 insertions, 12 deletions
diff --git a/builds.sr.ht/triggers.md b/builds.sr.ht/triggers.md
index e21ba06..0fb3148 100644
--- a/builds.sr.ht/triggers.md
+++ b/builds.sr.ht/triggers.md
@@ -5,18 +5,6 @@ title: Build triggers reference
At the end of a job or a job group, you can execute triggers based on the
outcome of the job.
-The basic format of a trigger is (in JSON):
-
-```
-{
- "action": "trigger type",
- "condition": "when to execute this trigger",
- [...action-specific configuration...]
-}
-```
-
-Or in YAML:
-
```
triggers:
- action: trigger type
@@ -53,3 +41,7 @@ request to a specified URL.
*Configuration*
- **url**: The URL to submit the HTTP request to
+
+## others?
+
+Patches welcome!