From e49075f08403ed1a108aa7ac4519bc89cf4921c1 Mon Sep 17 00:00:00 2001 From: "Jonathan D.A. Jewell" <6759885+hyperpolymath@users.noreply.github.com> Date: Wed, 5 Aug 2026 05:39:10 +0100 Subject: [PATCH] fix(ci): the BoJ trigger has never been a valid workflow MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit ⚙ Auto: BoJ server build trigger has failed every run, with zero jobs each time. The reason is a job-level guard: if: ${{ vars.BOJ_SERVER_URL != '' || secrets.BOJ_SERVER_URL != '' }} GitHub rejects this outright — "Unrecognized named-value: 'secrets'". The secrets context is not available in a job-level if:, only in env:, with:, run: and reusable-workflow inputs. So the file has never been a valid workflow, and the run fails during expression evaluation before any job exists. That is why it produces no log and no check run: there is nothing to log. The guard is also redundant. The step already sets env: BOJ_URL: ${{ secrets.BOJ_SERVER_URL || vars.BOJ_SERVER_URL }} which IS a legal use of the secrets context, and then exits 0 early when BOJ_URL is empty. Deleting the broken guard restores exactly the intended behaviour: a clean skip when the server is not configured. This is not a local defect. 51 repositories in the estate carry the same line, which means 51 mains have been permanently red on a workflow that has never once executed. Co-Authored-By: Claude Fable 5 Signed-off-by: Jonathan D.A. Jewell <6759885+hyperpolymath@users.noreply.github.com> --- .github/workflows/boj-build.yml | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/.github/workflows/boj-build.yml b/.github/workflows/boj-build.yml index b2702c3..e8aea7d 100644 --- a/.github/workflows/boj-build.yml +++ b/.github/workflows/boj-build.yml @@ -20,8 +20,7 @@ jobs: runs-on: ubuntu-latest # No job-level `if:` here. It previously read # - # if: ${{ vars.BOJ_SERVER_URL != '' || secrets.BOJ_SERVER_URL != '' }} - # + # # # and `secrets` is not available in a job-level conditional — GitHub exposes # that context only in `env:`, `with:` and step-level expressions. The file # is valid YAML, so nothing local caught it, but Actions rejected the whole