Skip to content

Prune stale merged and abandoned remote branches #441

@chubes4

Description

@chubes4

Problem

The repo has many remote branches left behind after merged PRs and older feature/refactor attempts. Some are merged into main; others appear abandoned or superseded.

This makes branch searches noisy when tracking whether runtime cleanup work is still pending.

Scope

Audit remote branches and classify them as:

  • merged and safe to delete.
  • generated/evidence branches that should be retained or expired under a policy.
  • abandoned work that should be linked to an issue or deleted.
  • active work that should have an open PR or tracker.

Acceptance criteria

  • Merged branches for closed PRs are deleted or explicitly retained with a reason.
  • Unmerged branches are mapped to open PRs/issues or removed when superseded.
  • Any branch retention policy is documented briefly so future audits are not ambiguous.
  • No active work is deleted without confirming its tracker/owner.

Evidence

A branch audit showed stale merged issue branches such as fix/issue-261-runtime-action-adapter, fix/issue-287-wordpress-state-artifacts, and fix/issue-288-browser-actions, plus many older feature/refactor branches still present remotely.

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