Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 27 additions & 0 deletions .issueflows/03-solved-issues/issue267_original.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
# Issue #267: chore: remote branch audit (2026-09-12)

Source: https://github.com/jepegit/issue-flow/issues/267

## Original issue text

## Remote branch audit

From `/iflow-cleanup github` on 2026-09-12 (`issue-flow agent branches`).

### Deletable
None — no remote heads were safe to delete. Squash-landed `265-howto-subchapters` was already gone from `origin` (likely auto-delete on merge of #266).

### Unique work (do not delete without review)

| Branch | Unique commits | Notes |
| --- | --- | --- |
| `140-agent-queue-cli` | 3 | No open/merged PR linked. Subjects: agent queue, epic-status, `/iflow-epic` publish + draft surface. |
| `cursor/163-github-branches-e2ca` | 5 | Merged PR #188 (2026-07-20) but tip still differs from `main`. |
| `cursor/gha-sync-issueflows-08d1` | 4 | Merged PR #160 (2026-07-13) but tip still differs from `main`. |

### Skipped
- `main` (default)

### Suggested follow-up
- Eyeball the three unique-work remotes; delete by hand only if the tip work is discarded or recovered elsewhere.
- Local `258-agent-name-issue-no-confirm` also has unique work after #259 — not a remote-audit item, but same hygiene class.
21 changes: 21 additions & 0 deletions .issueflows/03-solved-issues/issue267_plan.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
# Plan — Issue #267: chore: remote branch audit (2026-09-12)

## Goal

Record that the three audited remotes were deleted after review, and
close the findings issue. No new product code.

## Approach

The 2026-09-26 re-audit found the same three remotes. Their tips were
already-landed work (rebased or squash-merged). The user deleted them.
This close records that in `HISTORY.md`.

## Files to touch

- `HISTORY.md`
- Issue tracking files, moved to `03-solved-issues/`

## Test strategy

No new tests. Full `uv run pytest` before close.
13 changes: 13 additions & 0 deletions .issueflows/03-solved-issues/issue267_status.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
# Status — Issue #267: chore: remote branch audit (2026-09-12)

- [x] Done

## What's done

- Re-audited the three remotes. Work had already landed.
- User deleted `140-agent-queue-cli` (`111c6fb`), `cursor/163-github-branches-e2ca` (`6302079`), and `cursor/gha-sync-issueflows-08d1` (`d765ca5`).
- HISTORY `[Unreleased]` bullet written in the close commit. No version bump.

## Remaining work

- None.
1 change: 1 addition & 0 deletions HISTORY.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,7 @@ than the GitHub release notes they link to.

- Epic #269 is complete: user-global config, per-repo lock, the project registry, and `update --all` shipped in stages #281–#298. (#269)
- Skills that create multi-line GitHub text now say to use `--body-file` or `git commit -F`. Bash `<<'EOF'` heredocs fail in Windows PowerShell. (#380)
- The 2026-09-12 remote-branch audit's three stale remotes were deleted after review: `140-agent-queue-cli`, `cursor/163-github-branches-e2ca`, and `cursor/gha-sync-issueflows-08d1`. Their work had already landed. (#267)

## [0.5.15] - 2026-09-26

Expand Down
Loading