[PROBE — DO NOT MERGE] ersatztv#672 experiment A: is a pull_request workflow definition head-resolved? #693

Closed
timothy wants to merge 1 commits from scratch/672-head-a into scratch/672-base-a
Owner

Throwaway probe PR for ersatztv#672 Done-when box 1. Do not merge; both branches are deleted after the result is read.

Base and head are scratch branches, not main. Both sides have docker-build.yml and pr-checks.yml removed so this exercises review-verdict.yml alone rather than a full build.

The head commit rewrites .gitea/workflows/review-verdict.yml. The rewritten copy posts a distinct probe context (review-verdict/h10-PROBE672) and deliberately never posts the real review-verdict/h10, so the experiment cannot forge a green on the required check.

Read the result as:

  • probe context present, h10 absent → the definition came from the HEAD (the #672 hole is real)
  • h10 present, probe context absent → the definition came from the BASE (not vulnerable)

Refs #672

**Throwaway probe PR for ersatztv#672 Done-when box 1. Do not merge; both branches are deleted after the result is read.** Base and head are scratch branches, not `main`. Both sides have `docker-build.yml` and `pr-checks.yml` removed so this exercises `review-verdict.yml` alone rather than a full build. The head commit rewrites `.gitea/workflows/review-verdict.yml`. The rewritten copy posts a **distinct probe context** (`review-verdict/h10-PROBE672`) and deliberately never posts the real `review-verdict/h10`, so the experiment cannot forge a green on the required check. Read the result as: - probe context present, `h10` absent → the definition came from the **HEAD** (the #672 hole is real) - `h10` present, probe context absent → the definition came from the **BASE** (not vulnerable) Refs #672
timothy added 1 commit 2026-07-28 21:06:31 +02:00
scratch(672): probe head A — rewrite review-verdict.yml in the PR itself
Review verdict / Set review-verdict status (pull_request) Successful in 2s
review-verdict/h10-PROBE672 ersatztv#672 probe: posted by a HEAD-supplied workflow definition
ccbc4abbe0
Throwaway. Answers Done-when box 1: if this rewritten definition is what runs,
Gitea resolves a pull_request workflow definition from the PR head.

Posts a distinct probe context, never the real review-verdict/h10.
Not for merge.
timothy closed this pull request 2026-07-28 22:44:52 +02:00
timothy deleted branch scratch/672-head-a 2026-07-28 22:44:54 +02:00

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.