Repository navigation
feat: require a Task identifier line in the PR body - #103
Conversation
There was a problem hiding this comment.
Both changed workflows are sound: the new check-task-link gate consumes the attacker-controlled PR body through a quoted PR_BODY env var (no inline interpolation), runs on pull_request with contents: read and no third-party actions, and the ci.yml Trivy install is version-pinned and checksum-verified before extraction, failing closed on mismatch. Deterministic tier ran (0 findings), judgment tier selector ran (no violations; one non-blocking nit), security tier skipped (--security not requested), precommit skipped (selector mode — CI covers lint+test); operational note: the ruleset required-check context will be the job id task-link, not the workflow name check-task-link, per the repo's sibling-workflow convention.
Adds a
check-task-linkworkflow that fails a PR whose body carries noTask: <task_identifier>line.The identifier must be a UUID, not a title. A title does not survive a rename, and the vault resolves identifiers rather than names.
Also fixes this repo's
testcheck, red on every PR since 2026-11-14: the Trivy install used the retired apt keyring helper. Replaced with a pinnedv0.76.2release verified by sha256.Wiring: the workflow alone is advisory until
task-linkis added to the ruleset's required checks — a separate, operator-gated step.Task: 7c73a03d-8e9e-48e3-b6cf-556e788c7a8b