Protected branch name patterns. See the documentation for pattern syntax. Examples: main, release/**
Protected files are not allowed to be changed directly even if user has rights to add, edit, or delete files in this branch. Multiple patterns can be separated using semicolon (';'). See github.com/gobwas/glob documentation for pattern syntax. Examples: .drone.yml, /docs/**/*.txt.
.drone.yml
/docs/**/*.txt
Unprotected files that are allowed to be changed directly if user has write access, bypassing push restriction. Multiple patterns can be separated using semicolon (';'). See github.com/gobwas/glob documentation for pattern syntax. Examples: .drone.yml, /docs/**/*.txt.
No pushing will be allowed to this branch.
Anyone with write access will be allowed to push to this branch (but not force push).
Only allowlisted users or teams will be allowed to push to this branch (but not force push).
Reject pushes to this branch if they are unsigned or unverifiable.
No force pushing will be allowed to this branch.
Anyone with push access will be allowed to force push to this branch.
Only allowlisted users or teams with push access will be allowed to force push to this branch.
Allow only to merge pull request with enough required approvals. Required approvals are either from users or teams who are on the allowlist or anyone with write access.
Only reviews from allowlisted users or teams will count to the required approvals. Without approval allowlist, reviews from anyone with write access count to the required approvals.
When new commits that change the content of the pull request are pushed to the branch, old approvals will be dismissed.
Do not count approvals that were made on older commits (stale reviews) towards how many approvals the PR has. Irrelevant if stale reviews are already dismissed.
Require status checks to pass before merging. When enabled, commits must first be pushed to another branch, then merged or pushed directly to a branch that matches this rule after status checks have passed. If no contexts are matched, the last commit must be successful regardless of context.
Enter patterns to specify which status checks must pass before branches can be merged into a branch that matches this rule. Each line specifies a pattern. Patterns cannot be empty.
Anyone with write access will be allowed to merge the pull requests into this branch.
Allow only allowlisted users or teams to merge pull requests into this branch.
Allowlisted users or teams can merge or push even when required approvals, status checks, or protected-file rules would otherwise block them.
Merging will not be possible when changes are requested by official reviewers, even if there are enough approvals.
Merging will not be possible when it has official review requests, even if there are enough approvals.
Merging will only be possible if at least one code owner per code owner rule has given an approving review.
Merging will not be possible when head branch is behind base branch.
Administrators must follow branch protection rules and cannot circumvent it. Users or teams in the bypass allowlist can still bypass these rules if bypass allowlist is enabled.