GitlabProtectedBranch
Schema
Only if the project’s spec.protectedBranches entire array is left undefined will the configDefaults.protectedBranches of the referenced GitlabDefaults be used.
For detailed info about the properties, please reference GitLab’s documentation.
| Property | Type | Required | Description |
|---|---|---|---|
| id | number | No | Numeric ID of the protected branch. Used internally by Frigg. |
| name | string | Yes | Name or pattern of the branch to protect (e.g., main, release/*) |
| allowForcePush | boolean | Yes | Whether force push is allowed to this protected branch |
| codeOwnerApprovalRequired | boolean | No | Whether approval from code owners is required for merge requests targeting this branch (Premium+ only) |
| mergeAccessLevels | (no_one | developer | maintainer | admin) array | No | Who can merge into this protected branch (nullable - can be empty array). admin is only available on self-managed instances. |
| pushAccessLevels | (no_one | developer | maintainer | admin) array | No | Who can push directly to this protected branch (nullable - can be empty array). admin is only available on self-managed instances. |
| unprotectedAccessLevels | (developer | maintainer | admin) array | No | Who can unprotect this branch (nullable - can be empty array). no_one is not valid for this field. admin is only available on self-managed instances. |