Skip to content

Bug reports auto-labelled for Paperclip mirroring

Saga the Watchful — Ops Engineer

By the end of this chapter you’ll understand:

  • Why the paperclip label is the trigger for Ravens’ inbox-sync pipeline
  • What the before/after looks like in github_commands.rs
  • How this closes the Astrid → Ravens → CAS loop end-to-end

Bug reports auto-labelled for Paperclip mirroring

Status: Delivered
CAS: CAS-2856
Delivered: 2026-05-15
PRs: #795

What’s new

Every bug report filed through the Astrid sheet now arrives on GitHub with the paperclip label applied automatically. Ravens picks up the label and mirrors the issue into Paperclip as a CAS within one polling cycle.

What changed

Before: Astrid’s report_issue Tauri command created GitHub issues with bug or improvement plus a priority:* label, but omitted the paperclip label. Bug reports sat on GitHub indefinitely without being mirrored; the triage queue had to be populated manually.

After: post_issue_http in github_commands.rs now appends paperclip to the label list for every report_issue call, regardless of category or priority. Ravens mirrors the issue into Paperclip and closes the GH issue once the CAS reaches done.

Why we built it

Ravens’ inbox-sync pipeline is triggered exclusively by the paperclip label. Without it, user-filed bug reports were invisible to the automated triage pipeline and required manual intervention to reach an engineer. Adding the label at creation closes the loop: Astrid files → Ravens mirrors → CAS lands in the todo queue.

Recap

  • post_issue_http in github_commands.rs now appends paperclip to every report_issue call, regardless of category or priority.
  • Ravens’ inbox-sync pipeline triggers exclusively on the paperclip label — without it, user bug reports were invisible to automated triage.
  • The full loop is now: Astrid files → Ravens mirrors → CAS lands in the todo queue.

What changed {#what-changed}

See: CHANGELOG → 2026-05-18