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.
I1208 · web-sign-in · p1 · wave 6
Adding a provider is one file, removing one is one deletion, and both are executed rather than described
Document how a provider is added and how one is struck, and make the documentation executable: a test that adds a synthetic provider object and asserts it appears in the sign-in offer, in the capability read, in the generated documentation and in the Cockpit with no other edit, and a test that removes one of the two shipped objects and asserts every one of those surfaces loses it.
- Unblocks
- none
- Serves
- none
- Scope
docssiteapps/majordomus-cli/teststest/cases.ai/repo/rules/project- Evidence
- 0 of 3
- 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.