From 285053ac1edba680d7cd83ae04bbe160ab80b122 Mon Sep 17 00:00:00 2001 From: Luke Cheung Engle <99493186+luke-engle@users.noreply.github.com> Date: Tue, 20 Sep 2022 13:32:02 -0700 Subject: [PATCH] Update gitlab/5-custom-transformers.md Co-authored-by: Ethan Dennis --- gitlab/5-custom-transformers.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/gitlab/5-custom-transformers.md b/gitlab/5-custom-transformers.md index 15b30e5..9b29f96 100644 --- a/gitlab/5-custom-transformers.md +++ b/gitlab/5-custom-transformers.md @@ -153,9 +153,7 @@ Now you can perform another `dry-run` command with the `--custom-transformers` C Finally, you can use custom transformers to dictate which runners the converted workflows should use. To do this, answer the following questions: 1. What is label of the runner in GitLab to update? - - Since there is no `tags` stanza defined in the `terraform-example` project in GitLab, you will need to use the Ruby symbol for the default runner: - - __:default__ + - __:default__. This is a special keyword to define the default runner to use. You can optional target specific `tags` in a job. 2. What is the label of the runner in Actions to use instead? - __custom-runner__