Branch Protection
Previous steps
Branch protection should be enabled once development has been stabilized and delivered to another environment, such as QA or production. Release branches must be protected immediately after delivery.
Where do you work?
Currently, Studio does not include a branch protection functionality, so this configuration must be applied directly in GitLab.
Branch protection helps prevent accidental changes to sensitive or stabilized branches by blocking direct commits or, depending on the configuration, even merge requests. Since Studio does not provide a visual indicator for protected branches, it is important to anticipate this situation and inform the team about which branches are protected.
This feature applies only to entities versioned in Git, meaning that entities stored in the database can still be modified from Studio after a branch has been protected.