From 438c967eba0aa6de71ad308fe055b377bd52ad63 Mon Sep 17 00:00:00 2001 From: j-dunham Date: Mon, 15 Aug 2022 18:18:34 -0400 Subject: [PATCH] Update gitlab/valet-custom-transformers-lab.md Co-authored-by: Begona Guereca --- gitlab/valet-custom-transformers-lab.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gitlab/valet-custom-transformers-lab.md b/gitlab/valet-custom-transformers-lab.md index 3bb07bb..f8bb01e 100644 --- a/gitlab/valet-custom-transformers-lab.md +++ b/gitlab/valet-custom-transformers-lab.md @@ -43,7 +43,7 @@ jobs: # # 'artifacts.terraform' was not transformed because there is no suitable equivalent in GitHub Actions ``` - We can see from the last line that `artifacts.terraform` was not transformed. In order for us to write a custom transformer for this we need to know the identifier. In general, the identifier will be the value between the backticks, which in this case is `artifacts.terraform`. This is how our custom transformer will target the correct step. -- The custom transformers file can have any name, but it is recommend that you use a `.rb` extension so the codespaces editor knows it is a ruby file and can provide syntax highlighting. +- The custom transformers file can have any name, but it is recommended that you use an `.rb` extension so the codespaces editor knows it is a ruby file and can provide syntax highlighting. - we have chosen the `actions/upload-artifacts` as our replacement so we should look at the action's [documentation](https://github.com/marketplace/actions/upload-a-build-artifact) to determine the correct final yaml ```yaml - uses: actions/upload-artifact@v3