Skip to content

Read at

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.

I1014 · capability-graph · p2 · wave 4

The relation view reads the graph and holds no data of its own

blockedPull requests that name itClose

Render the relation graph interactively from the generated data, with filters, focus, neighbour highlighting and deep links, loaded only where it is used and bounded in cost.

Depends on
I1002I1007
Blocked by
I1007
Unblocks
I1021I1024
Serves
none
Scope
share/cockpit/src
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.