Branching & Deployment

Modified Gitflow: main ← release/* ← develop ← feature branches. Only main deploys to production. Everything else is CI-only.

AI Agent Push Rules

CAN: push to the current feature branch only.

NEVER: merge branches, create PRs, push to main/develop/release/*, force-push, or delete remote branches.

The human handles all merges, PRs, and deployments.

Pre-Push Checklist (mandatory before every push)

pnpm lint          # zero errors required
pnpm build         # must compile successfully
git status         # no untracked files that should be committed

Push only when: lint passes, build passes, you understand every change, no experimental code. Any doubt → do not push.

Report: Lint: passed | Build: passed | 100% certain | Ready to push: <branch>

Deployment Reality

A fix on a feature branch is invisible to production until merged to main. Always tell the user: "This fix is on <branch>. It reaches production only after merge to main."

Quick Reference

Item	Value
Branch prefixes	feat/ fix/ refactor/ chore/ ci/ doc/ style/ test/
Commit format	<type>[scope]: <description> — imperative, lowercase, no period
Commit types	feat fix refactor doc style chore ci test perf build

References

• Branch flow & strategy
• Commit format details
• CI/CD pipeline