GitLab administration guides
These guides are for GitLab maintainers (who own a projectβs rules) and administrators (who run runners, secrets and integrations for many projects). The material is grouped into three topic pages; read them in this order when you set up a new project or group.
Reading path
Section titled βReading pathβ- Protected branches, approvals and code owners: decide who can change the default branch and who must review.
- Create and protect a branch: branch rules and wildcards.
- Protected branch permissions: push, merge, force push.
- Merge request approvals: approval rules and settings.
- Code Owners:
CODEOWNERSsections and required approvals. - Merge request and issue templates: description templates and variables.
- Push rules and server hooks: decide what can be pushed.
- Branch naming rules
- Commit message format
- Jira ID requirement
- Pre-receive server hooks: custom checks on GitLab Self-Managed.
- Runners, CI/CD variables and webhooks: the infrastructure pipelines and integrations depend on.
Contributors who only need to clone, open merge requests and resolve conflicts should read Contributor basics instead.
Where to go next
Section titled βWhere to go nextβ- GitLab start page: the full learning path, including CI/CD pipelines and GitLab Duo.
- GitLab Merge Train: keeping a busy default branch green.
- GitHub administration guides: the same tasks on GitHub.