Article version: Enterprise Server 2.20
Enabling force pushes to a protected branch
You can allow force pushes to a protected branch.
Protected branches are available in public repositories with GitHub Free, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server.
Anyone with admin permissions to a repository can enable force pushes.
By default, force pushes are blocked on all protected branches. When you enable force pushes to a protected branch, anyone with at least write permissions to the repository can force push to the branch, including those with admin permissions.
Enabling force pushes will not override any other branch protection rules. For example, if a branch requires a linear commit history, you cannot force push merge commits to that branch.
You cannot enable force pushes for a protected branch if a site administrator has blocked force pushes to all branches in your repository. For more information, see "Blocking force pushes to repositories owned by a user account or organization."
If a site administrator has blocked force pushes to the default branch only, you can still enable force pushes for any other protected branch.
You can automatically enforce protected branch settings for some or all branches in your repository. For more information, see "Configuring protected branches."
- On GitHub Enterprise, navigate to the main page of the repository.
- Under your repository name, click
- In the left menu, click Branches.
- Next to "Branch protection rules", click Add rule.
- Under "Branch name pattern", type the branch name or pattern you want to protect.
- Under "Rules applied to everyone including administrators", select Allow force pushes.
- Click Create.