From 35de427a22f5db5d138e4f681cc8efc653060592 Mon Sep 17 00:00:00 2001 From: Begona Guereca Date: Mon, 15 Aug 2022 12:24:58 -0700 Subject: [PATCH] Update valet-audit-lab.md --- 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 8cb5571..0e8f800 100644 --- a/jenkins/valet-audit-lab.md +++ b/jenkins/valet-audit-lab.md @@ -79,7 +79,7 @@ Under the `Job types` section, we can see that the `audit` command is able to su Under the `Build steps` section we can see a breakdown of the build steps that were used in these pipelines. - Supported: 12/16 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/16 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. +- Unknown: 3/16 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: 1/16 discrete build steps are considered unsupported by Valet. This could 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.