From 6f4efbcd66b235053736a809605d1892a4314b84 Mon Sep 17 00:00:00 2001
From: Vivswan Shah <58091053+Vivswan@users.noreply.github.com>
Date: Wed, 11 Nov 2026 23:54:41 -0500
Subject: [PATCH] test(pages): expect the enable notice's section key once

The scenario pages-enable-needs-build-type-or-source pinned the notice as the engine printed it when it prefixed every section line with its key, so the text read "pages: pages: declared ...". The engine now names a notice's section once, and a line that already leads with its key is left alone, so a run prints "pages: declared ..." and the pinned line no longer matched. The two changes landed minutes apart and each passed alone. Only the expectation moves: the scenario still forbids a POST and a PUT to the Pages endpoint and still pins the advice.
---
 .../pages/scenarios/pages-enable-needs-build-type-or-source.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/test/sections/pages/scenarios/pages-enable-needs-build-type-or-source.yml b/test/sections/pages/scenarios/pages-enable-needs-build-type-or-source.yml
index 0658e948..5f5fc5ac 100644
--- a/test/sections/pages/scenarios/pages-enable-needs-build-type-or-source.yml
+++ b/test/sections/pages/scenarios/pages-enable-needs-build-type-or-source.yml
@@ -17,7 +17,7 @@ expect:
     - "POST /repos/{repo}/pages"
     - "PUT /repos/{repo}/pages"
   stdout_contains:
-    - "::notice::pages: pages: declared in the settings file but GitHub Pages is not enabled on the repo, and GitHub enables a site only from build_type or source, so apply changes nothing"
+    - "::notice::pages: declared in the settings file but GitHub Pages is not enabled on the repo, and GitHub enables a site only from build_type or source, so apply changes nothing"
     - "declare build_type or source to enable the site, or remove the pages section"
     - "A fine-grained token missing the Pages permission gets the same answer"
   stdout_lacks: