From 3a57228be001b751217e7079ac7d2e10c4b71b55 Mon Sep 17 00:00:00 2001 From: Norman Abramovitz Date: Wed, 15 Apr 2026 21:08:36 -0700 Subject: [PATCH] silence container-push-base-images-develop workflow The workflow has failed on every develop push since it was added (28 of 28 recorded runs are failures, no successes). It pushes images to ghcr.io/anynines/ (anynines's GHCR namespace) but lives on cloudfoundry/stratos and uses GH_PACKAGES_USER / GH_PACKAGES_TOKEN secrets that have never been configured here. Drop the push trigger so develop pushes stop firing failed-build notifications. Keep workflow_dispatch so the workflow can be manually triggered if/when: - the secrets get configured for upstream publishing, OR - someone wants to test it ad-hoc Real fix is to either (a) move the workflow to the anynines/stratos fork where their secrets are accessible, (b) configure the secrets on cloudfoundry/stratos, or (c) delete the workflow if upstream doesn't actually want to publish to a vendor namespace. Pending that ownership decision. --- .../workflows/container-push-base-images-develop.yaml | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/.github/workflows/container-push-base-images-develop.yaml b/.github/workflows/container-push-base-images-develop.yaml index 2f065237f1..5dc137ccf9 100644 --- a/.github/workflows/container-push-base-images-develop.yaml +++ b/.github/workflows/container-push-base-images-develop.yaml @@ -1,9 +1,12 @@ name: container-push-base-images-develop +# Disabled push trigger pending decision on workflow ownership: it pushes to +# ghcr.io/anynines/ but lives on cloudfoundry/stratos and uses secrets +# (GH_PACKAGES_USER / GH_PACKAGES_TOKEN) that have never been configured here, +# so every develop push has failed since the workflow was added. Kept +# workflow_dispatch so it can still be triggered manually if/when the +# secrets are configured. on: - push: - branches: - - develop workflow_dispatch: jobs: