Open-source software for Joomla, Gitea, and web platforms. Home of MokoSuite, MokoGitea, and MokoCLI.
Tennessee
standards/Branch-Policy.-
Branch Policy
Branch Model
| Branch | Purpose | Merges From | Merges To |
|---|---|---|---|
main |
Production-ready stable | rc, fix/* |
— |
rc |
Release candidate testing | dev |
main |
dev |
Active development | feature branches | rc |
feature/* |
New features | dev |
dev |
fix/* |
Bug fixes | main |
main |
Rules
- Feature branches branch from
dev, PR back todev - Fix branches branch from
main, PR back tomain - Never force-merge to main — CI checks must pass before merging
- Always PR review before merge — check compile errors, API patterns, imports
- Protected branches (
main,rc,dev) require PR + CI pass - Delete branches after merge
PR Workflow
- Create feature/fix branch
- Push commits
- Open PR to target branch
- Update CHANGELOG.md
- PR review (check for compile errors, correct API patterns, import ordering)
- Merge (after CI passes)
CI Push Pattern
For pushing to protected branches from CI workflows:
- Create a temporary branch
- Push changes to temporary branch
- Create PR from temporary branch to target
- Merge PR via API
- Delete temporary branch
Revision History
| Date | Author | Changes |
|---|---|---|
| 2026-06-21 | jmiller | Initial consolidation; resolved dev/{desc} vs feature/* contradiction |