Repository navigation
Decide fate of three copilot/* branches with unmerged work and no PR #1764
Description
Surfaced during the 2026-08-20 branch cleanup, which took the repo from 30 local / 62 remote branches down to 4 local / 17 remote.
Every branch deleted in that pass was first verified merged, closed, or content-identical to dev. These three were left alone precisely because they hold real unmerged content and have no PR tracking them — so nothing surfaces them and nothing will ever merge them on its own.
| Branch | Commits ahead of dev |
Files | Last commit |
|---|---|---|---|
copilot/1592-review-fixes |
2 | 8 | 2026-08-09 |
copilot/agentic-workflows-review |
1 | 3 | 2026-08-08 |
copilot/sub-agent-charters-loading |
1 | 6 | 2026-06-06 |
Decide per branch
- Open a PR — if the work is still wanted as-is
- Cherry-pick the useful hunks onto a fresh branch off
dev— if it's partly stale - Delete — if superseded
copilot/sub-agent-charters-loading is from June and predates a large amount of churn, including the #1739 skill refactor. It may no longer apply cleanly, and its content may already have landed by another route. Check before investing effort.
Suggested approach
For each branch:
git diff origin/dev...origin/<branch> --stat
git log origin/dev..origin/<branch> --onelineThen judge whether the change is still relevant against current dev.
Recovery note
A record of every branch deleted in the 2026-08-20 cleanup — with full SHAs and the reason each was dropped — was written to the session artifacts folder. Deleted objects remain in the local object store until git gc prunes them (default 90 days), so anything can be restored with git branch <name> <sha> or git push origin <sha>:refs/heads/<branch>.
Activity
bradygaster commentedon Aug 20, 2026
Flight sequencing note — revised 2026-08-20.
Wave: excluded from the gh-aw findings/continuation graph.
Depends on: nothing in this stream.
Blocks: nothing in this stream.
Safe to run in parallel with: technically safe, but it should be handled as branch-debt triage rather than sequenced with the gh-aw workflow fixes.
Why excluded: this issue is about deciding the fate of three stale
copilot/*branches, not the Squad gh-aw workflow chain. I verified without checkout/switching that the branches still exist and are ahead oforigin/dev:copilot/1592-review-fixes(2 commits, 8 files),copilot/agentic-workflows-review(1 commit, 3 files), andcopilot/sub-agent-charters-loading(1 commit, 6 files). None is a prerequisite for #1772, #1748, #1756-#1759, #1761-#1763, #1768, or #1770.github-actions commentedon Aug 20, 2026
📋 Assigned to Flight (Lead)
Issue: #1764 — Decide fate of three copilot/* branches with unmerged work and no PR
Flight will pick this up in the next Copilot session.
bradygaster commentedon Aug 20, 2026
Closing — all 3 \copilot/*\ branches deleted. Their content is already on \dev\ by other routes.
Flight's triage confirmed:
Branches deleted as part of closing this issue (see below). Keeping stale branches with no PRs and no substantive diff against \dev\ is noise.