Managing a branch protection rule

About branch protection rules

You can create a branch protection rule in a repository for a specific branch, all branches, or any branch that matches a name pattern you specify with fnmatch syntax. For example, to protect any branches containing the word release, you can create a branch rule for *release*.

You can create a rule for all current and future branches in your repository with the wildcard syntax *. Because GitHub uses the File::FNM_PATHNAME flag for the File.fnmatch syntax, the wildcard does not match directory separators (/). For example, qa/* will match all branches beginning with qa/ and containing a single slash. You can include multiple slashes with qa/**/*, and you can extend the qa string with qa**/**/* to make the rule more inclusive. For more information about syntax options for branch rules, see the fnmatch documentation.

If a repository has multiple protected branch rules that affect the same branches, the rules that include a specific branch name have the highest priority. If there is more than one protected branch rule that references the same specific branch name, then the branch rule created first will have higher priority.

Protected branch rules that mention a special character, such as *, ?, or ], are applied in the order they were created, so older rules with these characters have a higher priority.

To create an exception to an existing branch rule, you can create a new branch protection rule that is higher priority, such as a branch rule for a specific branch name.

For more information about each of the available branch protection settings, see "About protected branches."

Creating a branch protection rule

When you create a branch rule, the branch you specify doesn't have to exist yet in the repository.

1. On your GitHub Enterprise Server instance, navigate to the main page of the repository.

2. Under your repository name, click Settings.

3. In the left menu, click Branches.

4. Next to "Branch protection rules", click Add rule.

5. Under "Branch name pattern", type the branch name or pattern you want to protect.

6. Optionally, enable required pull request reviews.

   • Under "Protect matching branches", select Require pull request reviews before merging.

   • Click the Required approving reviews drop-down menu, then select the number of approving reviews you would like to require on the branch.

   • Optionally, to dismiss a pull request approval review when a code-modifying commit is pushed to the branch, select Dismiss stale pull request approvals when new commits are pushed.

   • Optionally, to require review from a code owner when the pull request affects code that has a designated owner, select Require review from Code Owners. For more information, see "About code owners."

   • Optionally, if the repository is part of an organization, select Restrict who can dismiss pull request reviews. Then, search for and select the actors who are allowed to dismiss pull request reviews. For more information, see "Dismissing a pull request review."

7. Optionally, enable required status checks. For more information, see "About status checks."

   • Select Require status checks to pass before merging.
   • Optionally, to ensure that pull requests are tested with the latest code on the protected branch, select Require branches to be up to date before merging.
   • Search for status checks, selecting the checks you want to require.

8. Optionally, select Require conversation resolution before merging.

9. Optionally, select Require signed commits.

10. Optionally, select Require linear history.

11. Optionally, select Apply the rules above to administrators.

12. Optionally, enable branch restrictions.

    • Select Restrict who can push to matching branches.
    • Search for and select the people, teams, or apps who will have permission to push to the protected branch or create a matching branch.

13. Optionally, under "Rules applied to everyone including administrators", select Allow force pushes.

    For more information about force pushes, see "Allow force pushes."

14. Optionally, select Allow deletions.

15. Click Create.

Editing a branch protection rule

1. On your GitHub Enterprise Server instance, navigate to the main page of the repository.

2. Under your repository name, click Settings.

3. In the left menu, click Branches.

4. To the right of the branch protection rule you want to edit, click Edit.

5. Make your desired changes to the branch protection rule.

6. Click Save changes.

Deleting a branch protection rule

1. On your GitHub Enterprise Server instance, navigate to the main page of the repository.

2. Under your repository name, click Settings.

3. In the left menu, click Branches.

4. To the right of the branch protection rule you want to delete, click Delete.