One branch only — main

rule Sat Jun 20 2026 00:00:00 GMT+0000 (Coordinated Universal Time) rulesgitbranches

One branch only — main

Every repo in the chirag127/oriz* family has exactly one branch: main. No feat/*, fix/*, chore/*, release/*, develop, staging, or any other long-lived branch.

Why

The user is solo. There is no parallel work to merge, no integration hell, no "can I cherry-pick this back". Branches add ceremony without benefit at this team size.

Conventional-commits (conventional-commits.md) on main give every change a structured history; the commit message is the changelog. PR review is replaced by code review at commit authorship time (the user reviews before commit).

What this means concretely

• Commit straight on main in every repo.
• No PRs against the user's own repos. (PRs against external open-source projects, when contributing, are a different story.)
• The git workflow is: edit → git add -A → git commit -m "feat: ..." → (only on user say-so) git push origin main.
• Submodule pointer bumps are committed on the master's main after the submodule's own main is at the desired commit.

Exceptions

If a complex multi-step refactor needs an in-progress branch for checkpointing, that's fine — but it must be deleted (merged or discarded) before the conversation ends. No long-lived branches.

See also

• no-force-push-to-main.md
• conventional-commits.md
• AGENTS.md "Git" section