Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
35 changes: 35 additions & 0 deletions .github/workflows/quality.yml
Original file line number Diff line number Diff line change
Expand Up @@ -557,6 +557,30 @@ on:
required: false
type: boolean
default: true
hydra-gates-e2e-anchor-blocking:
# THE OPT-IN GATE-46 ALREADY INVITES AND NOTHING COULD ACCEPT.
#
# Gate-46 resolves both traceability tags by identical rules, but only
# `@spec` blocks; `@e2e` is report-only, and its warning ends "set
# HYDRA_GATE_SPEC_ANCHOR_E2E_BLOCKING=1 for this repo once they are
# worked down". That instruction was unreachable. The gate step's `env:`
# block is fixed in this file, and a reusable workflow does not inherit
# `env` from its caller, so no app repo could set the variable however
# it wrote its own workflow. Measured 2026-09-10: the string appears
# nowhere in the organisation except the runner and the runner's own
# test — zero repos had opted in, and none could have.
#
# Same shape and the same reasoning as gates 112, 113, 114 and 115,
# which carry the identical "set HYDRA_GATE_<X>_BLOCKING=1 for this
# repo" invitation and are, today, equally unreachable. Wiring one flag
# per input is deliberate: a single passthrough for arbitrary
# HYDRA_GATE_* variables would let a caller silently disable a blocking
# gate, which is the opposite of what these opt-ins are for. Each new
# one is a visible, named line in the caller's workflow.
description: "Make gate-46 (spec-anchor-existence) BLOCK on unresolved `@e2e` anchors, not just on `@spec`. OPT-IN, default false, and it must stay opt-in: #726 counted 194 dangling @e2e anchors fleet-wide with 154 of them in four repos (dossiq 46, zaakafhandelapp 43, pipelinq 36, decidesk 29), so blocking on day one would turn the four repos with the MOST end-to-end coverage red on debt no PR introduced. The count is printed on every run either way — turning this on changes the verdict, not the visibility. Turn it on for a repo only once its @e2e count is measured at zero, with the gate's own resolver (scripts/lib/check_spec_anchors.py) rather than a reimplementation: three published figures for a comparable set were wrong on 2026-09-10 and every wrong one came from a hand-rolled resolver. `@spec` blocks regardless of this flag, exactly as it has since #246."
required: false
type: boolean
default: false

# ── Cost controls (measured 2026-08-27, .github#5xx) ──────────────────
#
Expand Down Expand Up @@ -7296,6 +7320,17 @@ jobs:
# The author's own head commit, so the fallback stops reading the
# merge commit. Empty on a push, where `git log -1` is already right.
HYDRA_GATE_HEAD_SHA: ${{ github.event.pull_request.head.sha }}
# Gate-46's `@e2e` half blocks only where the caller asked for it.
#
# Passed as an explicit '1'/'0' rather than the boolean's own string
# form. The runner compares against the literal "1"; a GitHub boolean
# interpolates as "true"/"false", which would read as "not 1" and
# leave the gate report-only in a repo that had opted in — a flag that
# says it is on, a gate that is off, and nothing in the log to tell
# them apart. Set unconditionally so the variable's value always comes
# from the caller's declaration rather than from whatever the runner
# defaults to.
HYDRA_GATE_SPEC_ANCHOR_E2E_BLOCKING: ${{ inputs.hydra-gates-e2e-anchor-blocking && '1' || '0' }}
run: |
set -u
ARGS="--app-dir ${GITHUB_WORKSPACE}/app"
Expand Down
Loading