Audit of every branch on the remote that is not main. One of the three
needs an owner decision; the other two are unambiguously dead.
chore/align-repo-policies — already gone, nothing lost
TODO.md's "Next Step" still instructs the reader to land this branch and
its "uncommitted work (32 modified Go files, new untracked .golangci.yml
and TODO.md)", citing commit 7d9a138.
That branch does not exist. It is not on the remote, not in any local clone
checked, and commit 7d9a138 is not present in the repository at all — git cat-file -t 7d9a138 fails, and it appears in no reflog.
Its content was superseded in full by work that has since landed or is in
flight: #56 (standardized repo policies), #58 (scripts-to-rule-them-all),
and #59 (canonical .golangci.yml plus the lint fixes across the Go files).
Nothing unmerged remains that is worth keeping. No action beyond
correcting the stale TODO.md reference, which is covered by #76.
fix/go-version-bump — superseded, safe to delete
Single commit 7cdb1fe, "fix: bump go directive from 1.17 to 1.22
(closes#33)". main is already on go 1.23, which is ahead of what this
branch proposes. Landing it would be a downgrade. The underlying issue #33
is closed and the fix reached main via #34.
Recommendation: delete the remote branch.
sneak-patch-1 — owner decision
Single commit d37f3c1, "add link to styleguide", authored by sneak. It
adds two lines to the README Participation section:
The README already points at REPO_POLICIES.md, which links to the
current code styleguides in the prompts repo. This would be a second,
competing pointer.
The link target is git.eeqj.de/sneak/styleguide, which does not appear
to be where the styleguides live now — they are under git.eeqj.de/sneak/prompts/prompts/. A README that ships a dead link is
worse than one that ships no link.
There is also a stray trailing space on the first added line and a deleted
blank line, so it would need a touch-up regardless.
Recommendation: drop the branch. The intent — point contributors at the
styleguide — is already served by the existing REPO_POLICIES.md link, and #75 is rewriting that part of the README anyway. If you want the styleguide
called out explicitly and separately, say so on #75 and it will be folded in
with a correct URL rather than landed as a stale one-off.
Definition of done
A decision on sneak-patch-1: land (with the URL corrected and whitespace
fixed), fold into #75, or delete.
fix/go-version-bump deleted from the remote.
main is the only long-lived branch, plus whatever is actively in flight.
Branch deletion on the remote is yours to do, so this is assigned to you.
Audit of every branch on the remote that is not `main`. One of the three
needs an owner decision; the other two are unambiguously dead.
## `chore/align-repo-policies` — already gone, nothing lost
`TODO.md`'s "Next Step" still instructs the reader to land this branch and
its "uncommitted work (32 modified Go files, new untracked `.golangci.yml`
and `TODO.md`)", citing commit `7d9a138`.
That branch does not exist. It is not on the remote, not in any local clone
checked, and commit `7d9a138` is not present in the repository at all —
`git cat-file -t 7d9a138` fails, and it appears in no reflog.
Its content was superseded in full by work that has since landed or is in
flight: #56 (standardized repo policies), #58 (scripts-to-rule-them-all),
and #59 (canonical `.golangci.yml` plus the lint fixes across the Go files).
**Nothing unmerged remains that is worth keeping.** No action beyond
correcting the stale `TODO.md` reference, which is covered by #76.
## `fix/go-version-bump` — superseded, safe to delete
Single commit `7cdb1fe`, "fix: bump go directive from 1.17 to 1.22
(closes #33)". `main` is already on `go 1.23`, which is ahead of what this
branch proposes. Landing it would be a downgrade. The underlying issue #33
is closed and the fix reached `main` via #34.
**Recommendation:** delete the remote branch.
## `sneak-patch-1` — owner decision
Single commit `d37f3c1`, "add link to styleguide", authored by `sneak`. It
adds two lines to the README Participation section:
> Ideally, contributions conform to @sneak's personal
> [code styleguide](https://git.eeqj.de/sneak/styleguide).
Two problems with landing it as-is:
1. The README already points at `REPO_POLICIES.md`, which links to the
current code styleguides in the `prompts` repo. This would be a second,
competing pointer.
2. The link target is `git.eeqj.de/sneak/styleguide`, which does not appear
to be where the styleguides live now — they are under
`git.eeqj.de/sneak/prompts/prompts/`. A README that ships a dead link is
worse than one that ships no link.
There is also a stray trailing space on the first added line and a deleted
blank line, so it would need a touch-up regardless.
**Recommendation:** drop the branch. The intent — point contributors at the
styleguide — is already served by the existing `REPO_POLICIES.md` link, and
#75 is rewriting that part of the README anyway. If you want the styleguide
called out explicitly and separately, say so on #75 and it will be folded in
with a correct URL rather than landed as a stale one-off.
## Definition of done
- A decision on `sneak-patch-1`: land (with the URL corrected and whitespace
fixed), fold into #75, or delete.
- `fix/go-version-bump` deleted from the remote.
- `main` is the only long-lived branch, plus whatever is actively in flight.
Branch deletion on the remote is yours to do, so this is assigned to you.
sneak
was assigned by clawbot2026-08-09 03:45:49 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Audit of every branch on the remote that is not
main. One of the threeneeds an owner decision; the other two are unambiguously dead.
chore/align-repo-policies— already gone, nothing lostTODO.md's "Next Step" still instructs the reader to land this branch andits "uncommitted work (32 modified Go files, new untracked
.golangci.ymland
TODO.md)", citing commit7d9a138.That branch does not exist. It is not on the remote, not in any local clone
checked, and commit
7d9a138is not present in the repository at all —git cat-file -t 7d9a138fails, and it appears in no reflog.Its content was superseded in full by work that has since landed or is in
flight: #56 (standardized repo policies), #58 (scripts-to-rule-them-all),
and #59 (canonical
.golangci.ymlplus the lint fixes across the Go files).Nothing unmerged remains that is worth keeping. No action beyond
correcting the stale
TODO.mdreference, which is covered by #76.fix/go-version-bump— superseded, safe to deleteSingle commit
7cdb1fe, "fix: bump go directive from 1.17 to 1.22(closes #33)".
mainis already ongo 1.23, which is ahead of what thisbranch proposes. Landing it would be a downgrade. The underlying issue #33
is closed and the fix reached
mainvia #34.Recommendation: delete the remote branch.
sneak-patch-1— owner decisionSingle commit
d37f3c1, "add link to styleguide", authored bysneak. Itadds two lines to the README Participation section:
> Ideally, contributions conform to @sneak's personal
> code styleguide.
Two problems with landing it as-is:
REPO_POLICIES.md, which links to thecurrent code styleguides in the
promptsrepo. This would be a second,competing pointer.
git.eeqj.de/sneak/styleguide, which does not appearto be where the styleguides live now — they are under
git.eeqj.de/sneak/prompts/prompts/. A README that ships a dead link isworse than one that ships no link.
There is also a stray trailing space on the first added line and a deleted
blank line, so it would need a touch-up regardless.
Recommendation: drop the branch. The intent — point contributors at the
styleguide — is already served by the existing
REPO_POLICIES.mdlink, and#75 is rewriting that part of the README anyway. If you want the styleguide
called out explicitly and separately, say so on #75 and it will be folded in
with a correct URL rather than landed as a stale one-off.
Definition of done
sneak-patch-1: land (with the URL corrected and whitespacefixed), fold into #75, or delete.
fix/go-version-bumpdeleted from the remote.mainis the only long-lived branch, plus whatever is actively in flight.Branch deletion on the remote is yours to do, so this is assigned to you.