A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:01:48Z by majordomus 0.29.0. Nothing on this page is read again. See it live
PR Drain
Pull requests converging on master, one at a time.
Every open pull request as the integration lane assessed it: what it waits for, what would move it, what it depends on and overlaps, and the issue it carries.
- Issues ready86plan.status /counts/by_status/READY
- Issues active1plan.status /counts/by_status/ACTIVE
- Issues blocked159plan.status /counts/by_status/BLOCKED
- Issues done161plan.status /counts/by_status/DONE
Issue
One issue of the plan, as the plan records it.
I2296 · test-evidence · p1 · wave 0
The executor reopens a record pull request no run was started for
Let `majordomus prs drain` close and reopen a release's record pull request itself when the workflow's token opened it and it therefore has no check of its own, so the record lands one validate cycle after publication without a person noticing.
- Depends on
- none
- Blocked by
- none
- Unblocks
- none
- Serves
- none
- Scope
apps/majordomus-cli/src/integration/drain.rsapps/majordomus-cli/src/integration/tests.rsapps/majordomus-cli/src/commands/prs.rsapps/majordomus-cli/tests/integration_record_reopen.rstest/cases/1036_the_executor_reopens_a_record_pull_request.shdocs/INTEGRATION.mdand 1 more- Evidence
- 2 of 2
- Started
- 2026-10-14 08:00:01Z
- Verified
- not yet
- Completed
- 2026-10-14 08:00:09Z
plan.issues0 msAPI/api/v1/plan/issuesMCPmajordomus_plan_issuestechnical view
Pull-request drain
The integration lane asks the forge for every open pull request; this takes a while and arrives after the screen.