From 5417017c1c0e54618df571a908e28949c8559e47 Mon Sep 17 00:00:00 2001 From: Begona Guereca Date: Fri, 12 Aug 2022 09:34:54 -0700 Subject: [PATCH] Update jenkins/valet-audit-lab.md Co-authored-by: j-dunham --- jenkins/valet-audit-lab.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/jenkins/valet-audit-lab.md b/jenkins/valet-audit-lab.md index 9f4f810..5a11e94 100644 --- a/jenkins/valet-audit-lab.md +++ b/jenkins/valet-audit-lab.md @@ -80,7 +80,7 @@ Under the `Build steps` section we can see a breakdown of the build steps that w - Supported: 7/9 discrete build steps are considered known by Valet. When Valet encounters a build step of this type, it knows exactly how to map that into a GitHub Actions equivalent. - Unknown: 2/9 discrete build steps are considered unknown by Valet. When Valet enounters a build step of this type, it does not yet know to map this automatically to a GitHub Action equivalent. -- Unsupported: There are currently no build steps that are unknown so this category is not shown. If there were unsupported steps, it would mean one of three things: +- Unsupported: There are currently no build steps that are unsupported so this category is not shown. If there were it would mean one of three things: 1. The way that plugin was configured for a given job is unsupported. 2. The plugin itself is fundamentally not supported in GitHub Actions. 3. It's supported by default in GitHub Actions.