From a50eeedac04921f4f6b1997b87240b7a9fe65a89 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tiago=20Ara=C3=BAjo=20=5BSSW=5D?= Date: Mon, 7 Oct 2024 22:22:20 -0700 Subject: [PATCH] =?UTF-8?q?XS=E2=9C=94=20=E2=97=BE=20Fixed=20captions=20"/?= =?UTF-8?q?complete-major-changes-on-another-repo"=20(#9351)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Fixed captions "/complete-major-changes-on-another-repo" --- rules/complete-major-changes-on-another-repo/rule.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/rules/complete-major-changes-on-another-repo/rule.md b/rules/complete-major-changes-on-another-repo/rule.md index 92251e4bbf4..413b3b8db8b 100644 --- a/rules/complete-major-changes-on-another-repo/rule.md +++ b/rules/complete-major-changes-on-another-repo/rule.md @@ -17,7 +17,7 @@ When making significant changes to your pipeline, it's crucial to test them in a Examining a mistake directly in the GitHub YAML file can be error-prone and might not provide a clear understanding of the issue. ::: bad -![Figure: This should read needs: approval-gate](2023-09-14_14-05-04.png) +![Figure: Bad example - This should read "needs: approval-gate"](2023-09-14_14-05-04.png) ::: @@ -26,5 +26,5 @@ To safely test a pipeline, particularly one that deploys to production, it's imp By executing the pipeline and examining its graphical representation, errors or inefficiencies become more apparent. This visual insight aids in swiftly pinpointing and comprehending any issues. ::: good -![Figure: Pipeline Graph shows the issue instantly - Prod deployment and approval-gate in the wrong order](2023-09-14_14-11-09.png) +![Figure: Good exampele - Pipeline Graph shows the issue instantly - Prod deployment and approval-gate in the wrong order](2023-09-14_14-11-09.png) :::