Skip to content

docs(workspace): a PR body edit re-runs public-intake and blocks a merge #472

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
d6g8k5htny-coder merged 2 commits into from
Oct 21, 2026
Merged

docs(workspace): a PR body edit re-runs public-intake and blocks a merge #472

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e3b6437
docs(workspace): a PR body edit re-runs public-intake and blocks a merge
claude Oct 21, 2026
9a68e5f
Merge branch 'main' into claude/workspace-intake-edit-note-20261021
d6g8k5htny-coder Oct 21, 2026
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
9 changes: 9 additions & 0 deletions docs/WORKSPACE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -160,6 +160,15 @@ git rev-parse <sha>:<path> origin/main:<path> # two equal lines: same bytes
On 19 October 2026, main#330's head `88ff9223` was not in `main`, but its
`PROOF.md` blob was.

Editing a pull request's title or body re-runs the required `public-intake`
check, because its workflow listens for `pull_request_target` type `edited`.
While that run is queued or in progress, a guarded merge is refused with HTTP
405 ("Required status check `public-intake` is queued"). Once an integrator has
picked up a pull request, others record late facts in a comment instead of
editing the body, and an integrator that edits the body lets the new run finish
before merging. On 20 October 2026 this refused the first merge attempt on
main#450 and on main#467.

## Local navigation check

The landing workflow's `landing-checks` job first requires that the same run's
Expand Down
Loading