Gitlab
26 articles
- Branch protection enabled on default branch
- At least one reviewer required before merge
- Required commit signatures enforced on default branch
- External collaborator push access is restricted
- CI pipeline must pass before merge
- Required status checks configured before merge
- Changes require a pull request before merge
- Pull requests are not merged without review approvals
- Ensure group default member role is set to read-only or restricted
- Ensure two-factor authentication is enforced for group members
- Ensure project creation is restricted to trusted members
- Ensure project deletion and transfer is restricted to owners
- Ensure source branches are deleted after merge request merge
- Ensure default branch deletion is not allowed
- Ensure force pushes are not allowed on the default branch
- Ensure stale merge request approvals are dismissed when new commits are pushed
- Ensure default branch protection is enforced for maintainers and owners
- Ensure branch protection is enabled on the default branch
- Ensure conversation resolution is required before merging on the default branch
- Ensure at least one approval is required for code changes on the default branch
- Ensure Pull requests are not merged without review approvals
- Ensure signed commits are required on the default branch
- Ensure CI pipeline passes before merge
- Ensure protected tags are enabled to prevent tampering with releases
- Ensure public projects have a SECURITY.md file
- Ensure Secret Detection is enabled to detect sensitive data