Skip to content

[Gastown] Stale escalation beads for non-existent branches #2336

@kilo-code-bot

Description

@kilo-code-bot

What happened?

Multiple stale escalation beads about non-existent branches (gt/shadow/5f257e54, gt/maple/aaaeed29, gt/birch/aaaeed29, gt/ember/aaaeed29, gt/flint/744fa5b4). The refinery keeps generating escalations for branches that no longer exist. These are clogging the bead queue. The branches are old and were likely force-closed or deleted before review could complete, but the system keeps generating escalation beads for them.

Area

Merge Queue / Refinery

Context

  • Town ID: 770aae45-84f2-471b-83b2-ff040cd1a2f1
  • Agent: Mayor (021a0341-2b42-48e2-8e71-23e54bc2b815)

Filed automatically by the Mayor via gt_report_bug.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions