As of 4/10/2026, our website repo has 52 branches . Most of these are already merged or multiple years out of date.
Ideally, we should have fewer than five branches:
The main branch
Maybe a gh-pages branch, depending on our deployment strategy
Maybe 2-3 feature branches for active and ongoing website projects with multiple contributors
Members should contribute by forking the repo, and only repo owners should be allowed to add new branches.
Some of the current branches might have large projects, so we should review at a group meeting before making any changes.
To do:
Remove stale branches
Restrict non-owners' ability to add branches, if that's not already done
Confirm that the Wiki describes a forking contribution strategy, not a branching strategy
Determine an owner and long-term plan for any big project branches
Possible updates to README.md and CODE_OF_CONDUCT.md (see also Website contributions: code of conduct and/or tighter permissions #425
As of 4/10/2026, our website repo has 52 branches. Most of these are already merged or multiple years out of date.
Ideally, we should have fewer than five branches:
mainbranchgh-pagesbranch, depending on our deployment strategyMembers should contribute by forking the repo, and only repo owners should be allowed to add new branches.
Some of the current branches might have large projects, so we should review at a group meeting before making any changes.
To do: