Flows

/<owner>/<repo>/flows is one picture per repository (#9434): on the left what flows in — the origin it was forked from, the upstream and sources it follows, the npm packages its package.json pins with the newest release upstream — and on the right what flows out: its forks and the mirror it pushes to. Each line has its state and when it last moved. The page draws it as that picture (#9595): sources left, the repository's name between, followers right, stacked below 900 px as Flows in, Packages, Flows out; no script, and the arrows are decoration only.

Left out: the CHANGELOG sections between pin and newest (dropped until a lookup can read one within a byte bound); the nightly radar is below; code scanning (and the release block on a new high finding); per-line buttons (actions are listed under the columns); counting a fork's commits ahead of its parent; GitHub release tags; the all-repositories admin view is admin-flows.md. Each is its own pull on top of dep_latest and readFlows.

The nightly radar (#9592)

Every night at 05:07 UTC (src/nightly/radar.ts, scheduled by src/nightly/service.ts with the other nights; off in a preview or without FORGE_TOKEN) the radar reads upstream for every unarchived repository that pins packages and files what is worth taking (src/flows/file.ts): one issue per dependency, Update <name> to <version>, whose newest stable release is above the pin. The body says what changed, why it helps and what could break, by the size of the gap. Never a duplicate: a dependency with an open update issue gets none, and a release already filed (even if closed) is not filed again. On an autonomous repository the issue is assigned to a builder on the crew (the crew's own pick, so the week's pace still holds it) and the body says the crew takes it; otherwise it is assigned to the repository's owner and waits for a person. Running it now: there is no button that files; Read upstream releases now only refreshes the readings, and the filing happens at the night's slot (the same radarNight a test calls). The issues are authored as the repository's owner, like every other job's (flake hunt, culprit, keeper). Resilience shows when it last ran and what it filed.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs