Repository navigation
Delete merged branches #114
Description
Merged branches remain on GitHub. This automation's GitHub access can't delete branches, so the deletion needs to be done in the GitHub UI or with git push origin --delete <branch>.
Keep the #41 branch (claude/elegant-bohr-zn28zn) until #41 settles. That's a decision recorded on #48.
Generated by Claude Code
Activity
amar-python commentedon Oct 27, 2026
Evidence for closure. The product owner ran this on 27 Oct 2026 at 21:46 AEDT.
git push origin --delete …deleted 24 branches, every one of them fully merged intomain(git branch -r --merged origin/main, checked againstgit ls-remote):art-milestone-0;docs/…branches;feat/…branches (M2 and offline install);fix/…branches.Earlier the same day, the product owner deleted
docs/writing-style,feat/117-password-reset,fix/123-failed-uploads,fix/118-api-unreachable,fix/118-reload-dirandfix/119-local-times.Kept on purpose (not merged):
claude/elegant-bohr-zn28zn: PR Group tests into unit, system, SIT, performance, accessibility and UAT #41, kept until Group tests into unit, system, SIT, performance, accessibility and UAT #41 settles (Identify remote branch claude/elegant-bohr-zn28zn #48).wip/cosmetic-sign-in: kept when PR wip: cosmetic sign-in page (parked, no auth backend) (#47) #80 was closed.docs/security-md: open PR docs: add SECURITY.md (#57) — draft until the reporting address exists #79.docs/starter-guide: open PR docs: starter guide #63.fix/issue-45-integration-ci,gap-remediation-2026-09,web-plain-frontend: they contain work not onmain. Keeping or deleting them is the product owner's call.Generated by Claude Code