From 7afa58c5628cd993915dc227c21b837d75627792 Mon Sep 17 00:00:00 2001 From: Claude Code Date: Fri, 21 Aug 2026 21:57:00 +0000 Subject: [PATCH] CompletePipeline: publish Pages only from branches the environment admits The 'github-pages' environment admits the default branch and 'dev' only, so the deploy job on any other branch is failed by GitHub before a runner is assigned - one second, no steps, no log. Every feature-branch pipeline therefore shows a red job that has nothing to do with its changes, which is how a real failure gets overlooked. pyTooling fixed this in its own pipeline (pyTooling#297) by guarding the job. Repositories calling 'CompletePipeline.yml' cannot do that - they have no per-job 'if:' to add - so the guard belongs here, where it reaches every consumer at once. Co-Authored-By: Patrick Lehmann --- .github/workflows/CompletePipeline.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/workflows/CompletePipeline.yml b/.github/workflows/CompletePipeline.yml index 8ff0dcd1..de40f62a 100644 --- a/.github/workflows/CompletePipeline.yml +++ b/.github/workflows/CompletePipeline.yml @@ -469,6 +469,7 @@ jobs: && needs.PublishCoverageResults.result == 'success' && needs.StaticTypeCheck.result == 'success' && contains(inputs.documentation_steps, 'pages') + && (github.ref_name == github.event.repository.default_branch || github.ref_name == 'dev') }} with: doc: ${{ fromJson(needs.UnitTestingParams.outputs.artifact_names).documentation_html }}