diff options
| -rw-r--r-- | builds.sr.ht/compatibility.md | 2 | ||||
| -rw-r--r-- | tutorials/builds.sr.ht/using-build-secrets.md | 4 |
2 files changed, 3 insertions, 3 deletions
diff --git a/builds.sr.ht/compatibility.md b/builds.sr.ht/compatibility.md index 3b6a1db..92804b6 100644 --- a/builds.sr.ht/compatibility.md +++ b/builds.sr.ht/compatibility.md @@ -509,7 +509,7 @@ The packages array is installed with `dnf install`. Given the following list of repositories in your manifest: -```yml +```yaml repositories: example: https://example.org ``` diff --git a/tutorials/builds.sr.ht/using-build-secrets.md b/tutorials/builds.sr.ht/using-build-secrets.md index 4a6e5dd..f343c0a 100644 --- a/tutorials/builds.sr.ht/using-build-secrets.md +++ b/tutorials/builds.sr.ht/using-build-secrets.md @@ -12,7 +12,7 @@ available to CI jobs. Let's say we have a git repo with static HTML files that we'd like to deploy by sending them to our web server. A simple build manifest might look like this: -```yml +```yaml image: alpine/edge packages: - rsync @@ -65,7 +65,7 @@ UUID for the next step. This part is easy. We can simply add a list of secret UUIDs we want to be available in this build. -```yml +```yaml image: alpine/edge secrets: - c262b238-41de-4b43-a2f9-460424dd7896 |