At the end of a job or a job group, you can execute triggers based on the outcome of the job.
triggers:
- action: trigger type
condition: when to execute this trigger
...action-specific configuration...
Condition may be one of the following:
The following actions are available:
Sends an email summarizing the build results.
Configuration
Jim Jimson <jim@example.org>, Bob Bobson <bob@example.org>. Required.Submits the final job status as a POST request to a specified URL.
Configuration
The JSON payload POSTed to the provided URL looks something like this:
{
"id": integer,
"status": string,
"setup_log": url,
"note": string or null,
"runner": string or null,
"owner": {
"canonical_name": "~example",
"name": "example"
},
"tasks": [
{
"name": string,
"status": string,
"log": url
},
...
]
}
Patches welcome!
commit 0b2cece8723735483503b97574b18741d0710998 Author: fardog <nat@fardog.io> Date: 2026-01-07T20:47:09Z terms: fix language around content deletion This supersedes [#66048][], as I named the incorrect project name in the subject, which caused the build to fail. Original email is quoted below: [#66048]: https://lists.sr.ht/~sircmpwn/sr.ht-dev/patches/66048 A very small typo I noted in the terms of service; alternatively it could be corrected as "will not [be] displayed", but either one reads fine to me. No worries if the terms need more ceremony to be changed; was as easy to submit as a patch as it would've been to raise in the mailing list.