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.
I2484 · development-runtime · p1 · wave 1
majordomus ui ensures the shared server and opens the UI's dashboard
Give the primary surface its command: `majordomus ui` ensures this checkout's shared server, the way `serve ensure` does, prints the address of /ui and opens it in a browser, so that a person reaches the UI in one step and never needs the lease, a port or the Cockpit to find it.
- Depends on
I2461- Blocked by
- none
- Unblocks
- none
- Serves
- none
- Scope
apps/majordomus-cli/src/commandsapps/majordomus-cli/src/cli.rsapps/majordomus-cli/src/uidocs/MAJORDOMUS_UI.mdtest/cases.ai/repo/project/issues/I2484.yaml- Evidence
- 0 of 2
- Started
- not yet
- Verified
- not yet
- Completed
- not yet
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.