From 4ba306a0cb072a1fdf90594fa68b97e380b6b87c Mon Sep 17 00:00:00 2001 From: juliantellez <4896851+juliantellez@users.noreply.github.com> Date: Tue, 1 Sep 2026 08:19:50 +0000 Subject: [PATCH] docs: the subject to land is pull request 4, red on plan and apply --- docs/the-subject-is-pull-request-4.md | 123 ++++++++++++++++++++++++++ 1 file changed, 123 insertions(+) create mode 100644 docs/the-subject-is-pull-request-4.md diff --git a/docs/the-subject-is-pull-request-4.md b/docs/the-subject-is-pull-request-4.md new file mode 100644 index 0000000..c767ce2 --- /dev/null +++ b/docs/the-subject-is-pull-request-4.md @@ -0,0 +1,123 @@ +# The pull request to land + +Repository: `atlantic-blue/transcript`. I fetched first. Then I read. I read this on 1 September +2026. `origin/main` is at `3b5f6cc2038dfd13b17fc55714b525be076336e4`. + +Eleven pull requests are open. They are numbers 4 to 14. + +## The subject + +- Number: 4 +- Address: https://github.com/atlantic-blue/transcript/pull/4 +- Title: fix: report what the platform actually answered instead of a missing video +- Head branch: `diagnose-the-boundary-and-report-the-real-cause` +- Head commit: `84d9fe37c3414e82dc8937a7046a626cc590d8c0` +- Base branch: `main` +- Draft: no +- Conflicts with `main`: no +- Checks that are not passing: `plan and apply` + +Pull request 4 opened on 31 August 2026 at 11:30. It is the oldest of the eleven. It is the only +one with a check that is not passing. It qualifies on that check. It does not qualify on a conflict. + +## The three check runs on the head commit + +- `code`: completed, success +- `infrastructure`: completed, success +- `plan and apply`: completed, failure + +The failing job is here: + +https://github.com/atlantic-blue/transcript/actions/runs/33387270234/job/99472620061 + +That run is the only `deploy` run on this head commit. No later run replaced it. + +There is no commit status on this head commit. The combined status endpoint answers `pending` with +zero contexts. That is an absence, not a failure. It is the same on all eleven heads. + +## The usual command hides the failure + +`gh pr checks 4` prints two lines. It prints `code` and `infrastructure`. It calls both a pass. It +exits 0. It does not print `plan and apply`. Read the commit instead: + +``` +gh api repos/atlantic-blue/transcript/commits/84d9fe37/check-runs \ + --jq '.check_runs[] | "\(.name) \(.status) \(.conclusion)"' +``` + +That command answers with three names. `plan and apply` is a failure. + +The trigger is the cause. `plan and apply` is the only job in the `deploy` workflow. That workflow +starts on a push to `main` and on a manual start. Its `on:` block holds `push` and +`workflow_dispatch`. It holds no `pull_request`. So GitHub keeps the run out of the pull request +summary. The run on this head commit started as `workflow_dispatch`. + +An absent check reads the same as a passing one. Read the check runs on the head commit, never the +pull request summary. + +## No check is mandatory in this repository + +`repos/atlantic-blue/transcript/branches/main/protection` answers 404 with "Branch not protected". +`repos/atlantic-blue/transcript/rulesets` answers with an empty list. +`repos/atlantic-blue/transcript/rules/branches/main` answers with an empty list. + +So no check is mandatory, and no check blocks a merge. + +I read the test as "a check that is not passing". I did not read it as "a check that a branch rule +makes mandatory". I name that judgement here, because it decides the answer. Under the strict +reading nothing is eligible, and a real red check on the oldest pull request stays hidden. + +## The other ten open pull requests + +Each one is newer than pull request 4. Each one has two check runs, `code` and `infrastructure`, and +both pass. None conflicts with `main`. So none qualifies. + +- Number 5, `docs: name the pull request to land`, head `46b9460a`, opened 00:57 on 1 September. Adds `subject.md`. +- Number 6, `docs: the subject to land is pull request 4`, head `9597c60c`, opened 07:12. Adds `subject.md`. +- Number 7, `docs: name pull request 4 as the subject to land`, head `e44acfdb`, opened 07:13. Adds `subject.md`. +- Number 8, `docs: say what landing pull request 4 found`, head `c2878ae4`, opened 07:23. Adds `land.md`. +- Number 9, `docs: record pull request 4 as the subject to land`, head `d3ced9d9`, opened 07:33. Adds `docs/subject.md`. +- Number 10, `docs: record what landing pull request 4 found`, head `a258d485`, opened 07:44. Adds `docs/land.md`. +- Number 11, `docs: name pull request 4 as the subject to land`, head `b09ec2fc`, opened 07:51. Adds `docs/the-subject-to-land.md`. +- Number 12, `docs: record what landing pull request 4 found`, head `0a959240`, opened 07:58. Adds `docs/landing-pull-request-4.md`. +- Number 13, `docs: name pull request 4 as the subject to land`, head `f5f866f9`, opened 08:04. Adds `docs/subject-pull-request-4.md`. +- Number 14, `docs: record what landing pull request 4 found`, head `cd85b465`, opened 08:12. Adds `docs/land-pull-request-4-the-address-is-refused.md`. + +Pull requests 5, 6, 7, 9, 11 and 13 are the output of earlier rounds of this same task. Each one +names pull request 4. Pull requests 8, 10, 12 and 14 report the round that worked it. + +## The exclusions I checked + +- **Draft.** No pull request is a draft. `isDraft` is false on all eleven. +- **A head branch that another pull request is based on.** Every `baseRefName` is `main`. No pull + request is based on another pull request's head branch. So landing pull request 4 breaks no child. +- **Conflicts.** GitHub answers `MERGEABLE` and `CLEAN` for all eleven. I did not trust that alone. + I ran `git merge-tree --write-tree origin/main ` for each one. Each exits 0 and prints no + conflict line. + +## A collision that is already there + +Pull requests 5, 6 and 7 each add `subject.md` at the root of the repository. `main` holds no such +file, so none of the three conflicts with `main` today. The first of them to merge creates the file. +Then the other two conflict on add over add, and a person must resolve them by hand. + +The pull request that carries this report adds `docs/the-subject-is-pull-request-4.md`. No other +open pull request touches that path, so it conflicts with none of the ten. + +## What landing pull request 4 will find + +An earlier round worked pull request 4 to the end. Its report is at +`/home/agent/shared/land/land.md`, and it also ships as pull request 10 and pull request 14. The +short version: + +- The branch needs no merge. `origin/main` at `3b5f6cc` is an ancestor of the head. +- Every gate that can run in a sandbox passes on the branch. +- The red step is a correct gate. It asks the deployed page for a transcript. The page answers 502. +- Every `deploy` run in this repository failed, on `main` as well as on this branch. So pull + request 4 does not cause the failure. It inherits it. +- The cause is the address the function calls from. The platform sends a bot check to Amazon Web + Services Lambda in eu-west-1. The same code, run from this sandbox, reads 280 caption segments. + +I did not verify those readings again in this round. I verified the state that decides the pick: the +pull request list, the draft flag, the base branch, the mergeability, and the check runs on every +head commit.