diff options
Diffstat (limited to 'builds.sr.ht/index.md')
| -rw-r--r-- | builds.sr.ht/index.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/builds.sr.ht/index.md b/builds.sr.ht/index.md index 54e4518..831fa71 100644 --- a/builds.sr.ht/index.md +++ b/builds.sr.ht/index.md @@ -28,12 +28,12 @@ on. # How jobs are submitted Unlike some other build systems, builds.sr.ht does not let you configure builds -on the website itself. Instead, you write build *manifests* - YAML files that +on the website itself. Instead, you write build *manifests* — YAML files that tell builds.sr.ht what to do. You can then submit these manifests via the API and we'll assign a runner and execute your job. For convenience, there are ways of submitting builds automatically throughout -the sr.ht ecosystem - for example by pushing to repositories on git.sr.ht. +the sr.ht ecosystem — for example by pushing to repositories on git.sr.ht. These integrations are [discussed below](#integrations). For details on submitting jobs via the API, see the [API reference](api.md). @@ -55,7 +55,7 @@ tasks: When you submit this build, we'll fire up a virtual machine running an up-to-date image of Alpine Linux. Then, we'll copy your scripts into the machine and run them one at a time. More complex build jobs will probably use more -features of the build.yml - here's an example that deploys +features of the build.yml — here's an example that deploys [web.synapse-bt.org](https://web.synapse-bt.org): ```yaml @@ -201,7 +201,7 @@ submitted, 4 manifests will be randomly chosen). ## hg.sr.ht hg.sr.ht will also automatically submit builds for you. The naming conventions -and other details are the same as the process used by git.sr.ht - described +and other details are the same as the process used by git.sr.ht — described above. ## hub.sr.ht |