Skip to content

CONCEPT Cited by 1 source

Issue labels as workflow state

Issue labels as workflow state is the practice of using a tracker’s native labels, plus its timeline or comments, as the authoritative state record for a long-running workflow. A worker recovers by rereading the issue instead of consulting a private database; people can inspect and correct the same state record. (Source: sources/2026-08-04-cloudflare-astro-issue-triage)

Astro instance

Astro’s triage workflow starts a submitted issue at triage needed and changes it to fix verified after the reporter confirms a preview package. The automation holds no additional workflow state; it uses labels to determine the coarse state and reads issue comments to recover evidence and decide the next step. (Source: sources/2026-08-04-cloudflare-astro-issue-triage)

Consequences

  • Recovery and auditability align. The data used for resumption is also visible to maintainers and reporters.
  • No duplicate control-plane store. The issue tracker is the record of work and its state machine, reducing cross-system synchronization.
  • Human intervention is native. A maintainer can inspect, edit, or transition the same labels that drive automation.
  • State must remain disciplined. Labels need an explicit transition contract, authorization, idempotent workers, and conflict handling when multiple automations or people act concurrently; these controls are not described in the Astro post.

Seen in

Last updated · 622 distilled / 1,953 read