Organization and Repository Conventions
Consistent naming and structure across organizations and repositories makes automation and navigation much easier as the platform grows.
What this page covers
- Recommended Gitea organization structure
- Repository naming conventions
- Branch protection rules
- Suggested team permissions model
Organization structure
Organize repositories into Gitea Organizations by domain:
infra— infrastructure-as-code (Flux manifests, Helm values, Docker Compose stacks)apps— application source repositoriesagents— AI agent configuration and scripts
Repository naming
Use lowercase kebab-case: my-service, fleet-infra, doc.
Branch protection
Protect main on all repositories:
- Require pull request reviews before merge
- Require status checks to pass (CI)
- Disallow force pushes