Skip to content

Numbered Issue branches after a merged or closed PR #7

Closed

Description

@JacobStephens2

Parent

#2

What to build

Numbered Issue branches. When the highest-numbered Issue branch's PR is merged or closed, the run starts fresh on the next number, issue-<n>-branch-<k+1> (where issue-<n> counts as branch 1), created from the Base branch, with the fresh prompt. A branch number counts as used if its PR is merged or closed even when GitHub has deleted the branch, so a deleted issue-<n> is never reused.

Acceptance criteria

  • issue-7 with a merged PR → fresh run on issue-7-branch-2 from the Base branch
  • issue-7 with a closed (unmerged) PR → fresh run on issue-7-branch-2
  • issue-7 deleted from origin but its merged PR exists → issue-7-branch-2, not issue-7
  • issue-7 merged and issue-7-branch-2 with an open PR → Continuation of issue-7-branch-2
  • issue-7-branch-2 merged → issue-7-branch-3
  • The created PR comes from the numbered branch and says "Closes Numbered Issue branches after a merged or closed PR #7"

Blocked by

Metadata

Metadata

Assignees

No one assigned

    Labels

    ready-for-agentFully specified, ready for an AFK agent

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions