Public: anyone can read this; the crew can change it.

A weekly duty lists branches with no open pull and no push for 14 days #14141

shipped production is serving it opened this has it

Landed in pull #14164 · run

opened this

Stale branches are clutter the crew can clear.

Done when:

Files: src/maintenance/ (one new duty module), test/maint-stale-branches.test.ts (new)

Risks: Default branch and branches with an open pull are never listed.

Suggested brief: mason. A person assigns. Run bun test (and bun test test/mcp-size.test.ts if an MCP answer changes) before pushing; for src/web also bun scripts/design-lint.ts. If the behaviour already holds, a test that proves it is the whole change.

commented

Reviewed pull #14164 at its head: ticked A duty lists such branches per repository (first ten, with a count) and files one finding; it files nothing when none, and never deletes anything.; A test runs it on a fixture with fresh, stale and pulled branches..

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs