Answer prose round 1: 0 🔴, 11 🟡 (0 misread); the help lists merge's steps and stops, and the decision says where it differs from the call
CI / tests (pull_request) Successful in 2m45s

This commit is contained in:
2026-11-15 21:56:11 +01:00
parent 9e0a6d4d7b
commit e37518db29
+2 -2
View File
@@ -9,7 +9,7 @@ from chunk_preflight.gathered import Forge
from deploy_release.forge import Run
BIN = pathlib.Path(__file__).resolve().parents[1]
# A human answers in hours, so merge polls once a minute and gives up after 90 minutes, which leaves room for the checks wait inside the 2 hours a background command may run, so that the give-up message prints.
# A human answers in hours, so merge polls once a minute and gives up after 90 minutes. That leaves half an hour for the queue and the checks inside the 2 hours a background command may run; a run that needs more is killed before the give-up message prints, and its next run goes on from what it pushed.
POLL_SECONDS = 60
WAIT_SECONDS = 90 * 60
@@ -26,7 +26,7 @@ def awaited(forge: Forge, run: Run) -> bool | Failure:
return answer.strip() == "true"
# Each review thread nobody resolved, with who wrote its last comment, beside who opened the pull request. gh fills {owner} and {repo} from the checkout.
# Each review thread, with whether it is resolved and who wrote its last comment, beside who opened the pull request. gh fills {owner} and {repo} from the checkout.
THREADS = """query($owner: String!, $repo: String!, $number: Int!) { repository(owner: $owner, name: $repo) { pullRequest(number: $number) {
author { login }
reviewThreads(first: 100) { nodes { isResolved path comments(last: 1) { nodes { author { login } } } } }