Overview
MokoGIT lets you guard important branches at the repository level and set organization-wide governance that every repo inherits — a most-restrictive floor an individual repository cannot weaken.
Branch & tag protection
- Protected branches — require pull requests, a minimum number of approving reviews, and passing status checks before a merge; restrict who can push or merge.
- Delete allowlist — even for protected branches, you can permit specific users, teams, or deploy keys to delete them (useful for automated release/promotion flows).
- Tag protection — restrict who can create or delete matching tags (team allowlist), so release tags aren’t moved by accident.
Organization governance
Organization owners can layer rules onto every repository in the org:
- Branch protection floor — an org branch-protection rule is a minimum that a repo cannot relax, only tighten.
- Push policy — branch/tag naming rules, mandatory secret-blocking, a maximum file size, and blocked paths.
- Repository defaults — force new repos private, and preset the allowed PR merge styles.
- Member email-domain allowlist — restrict org membership to approved email domains.
Where to set it
- Per-repo: repository Settings → Branches / Tags.
- Org-wide: organization Settings → Governance / Policies. The same rules are available over the REST API for automation.
Get help
Open a support ticket or call (931) 279-6313.