Branch cleanup
@mdboom is already working on this.
Since Jun 10, 2026.
- Dominant language
- Cython
- Stars
- 3.4k
- Forks
- 329
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 116
Description
We should try to reduce the number of branches in the main fork of the project.
copy-pr-bot
Branches of the form pull-request/XXXX come from copy-pr-bot. This is a necessary part of the security of our CI, so we need to keep these around and live with the noise.
Coding-agent-created branches
Some users' coding agents seem to be creating branches on the main fork.
These ones have an open PR associated with them. Deleting them immediately would invalidate those PRs. We can just wait until these PRs are naturally merged or closed.
| Author | Branch | PR | Title |
|---|---|---|---|
| @kkraus14 | codex/docs-pyobj-reference-fixes | #2167 | [codex] Regenerate CUDA bindings docs references |
| @kkraus14 | codex/fix-cuda-bindings-problematic-doc-anchors | #2186 | [codex] Fix generated cuda-bindings problematic doc anchors |
| @kkraus14 | cursor/env-setup-830c | #2071 | Add Cursor Cloud specific instructions to AGENTS.md |
| @rwgk | check-release-notes_with_backport-git-tag | #2161 | [no-ci] Fix backport release checks and add release dry-run |
| @rwgk | rwgk/stacked/pathfinder/utils_driver_and_toolkit_info | #2012 | pathfinder: add toolkit-info parser and display-driver release helpers |
These branches do not have an open PR associated with them. They should be deleted if no longer required.
| Author | Branch |
|---|---|
| @kkraus14 | codex/fix-build-docs-pixi |
We should
- #2191 Add instructions to
AGENTS.mdto never do this - Each user should set upstream to read-only in their own checkout:
git remote set-url upstream --push "Don't push to me"
Other random branches
I think these were temporary experiments.
@leofang | ci/sanitizer-restrict-cuda13
Branch protection rules
- Set up rules so that new branches (other than the ones required by our bots) can not be created
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.