Branching Strategy

Branches

Branch	Purpose	Deploys
main	Stable releases	Publishes to public npm + updates Homebrew tap
release	Release candidates	Publishes RC to GitHub Packages (internal testing)
feat/*	New features	—
fix/*	Bug fixes	—
chore/*	Maintenance, tooling, docs	—

Flow

feat/my-feature ──→ main ──→ publish stable (npm + Homebrew)
                      │
                      └──→ release ──→ publish RC (GitHub Packages)

1. Create a feature branch from main (e.g. feat/add-retry-logic)
2. Make changes, commit, push
3. Open a PR targeting main
4. After review and merge, publish.yml publishes a stable release to public npm and syncs the Homebrew tap
5. For release candidates, merge main into release to trigger rc.yml, which publishes to GitHub Packages with the rc dist-tag

PR conventions

• Keep PRs focused on a single concern
• Branch names should use the feat/, fix/, or chore/ prefix
• Commit messages should be descriptive of the change