Count Patchula

Appearance

Dependency dashboard ​

pkl
prs { dashboard = true }

With the dashboard on, the Count keeps one issue per repository, titled "Count Patchula's dependency dashboard" to begin with. Rename it if you like: he finds it by a hidden marker and by who wrote it, not by title. Turning the dashboard off closes the issue; turning it on again opens a new one.

What it shows ​

In order:

  1. open update PRs, grouped by update type, then the ones he merged;
  2. pending updates, each with the reason it is held (release age with the time it becomes eligible, PR limits, schedule windows);
  3. updates you closed ("Updates you closed"), with the target that was suppressed, and updates "Batched by the Count";
  4. lookup warnings and sources served from stale cache;
  5. every detected dependency, collapsed by manager and file.

The issue body is bounded to GitHub's size limit. An unchanged dashboard is not rewritten: the Count compares the rendered content with the issue's actual body, so ticks and edits are noticed even when his own records say nothing changed.

Checkboxes ​

Ticking a box asks for one thing:

  • Re-check this repository: look everything up again and regenerate or rebase its branches. Release age, limits and your closures still apply to new updates.
  • Create a held-back update now: skip the release-age wait, PR limit or schedule window for that one update. Everything else, digest pins, lockfile generation and ownership checks, still applies.
  • Recreate a closed update: open a new PR for the same target and leave the old one closed.
  • Retry a failed lookup: fetch the source again despite cached freshness.

Each box is unticked once its action is done, or disappears when its row is resolved. Boxes are read on live runs only; lookup and --dry-run never consume them. The CLI's wording says the click takes effect "on the next run"; --recheck now or PATCHULA_RECHECK=now changes it for setups where a webhook starts a run straight away.

A box only counts when the Count's own hidden action marker is on that line and the issue is his. Copies made by someone else, duplicate actions and examples in code fences are ignored.

A release-age target you create early is remembered, in the cache and in a marker on the resulting PR, so a later run does not revert it while its wait is still running.