From 05f91f165b683da0843e6c497e0ae450da048580 Mon Sep 17 00:00:00 2001 From: Steven Guikal Date: Tue, 15 Dec 2020 19:46:34 +0000 Subject: Fix broken yaml highlighting --- tutorials/builds.sr.ht/using-build-secrets.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'tutorials') 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 -- cgit