state

Overview ¶

Package state prints what ar2's state says.

The state decides which package a run works on next, and nothing else can be asked about it: the repository says what the registry holds, not whose turn it is. So "why hasn't this package been generated" has no answer anywhere else, and neither has "how far along is the backfill" beyond counting branches.

It only reads, which makes it the one thing here that runs from a laptop: everything that writes has to be a workflow, because a commit made with a user access token isn't signed and the rulesets require signatures.