Anyone with admin permissions to a repository can enable force pushes.
About force pushes to protected branches
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 can automatically enforce protected branch settings for some or all branches in your repository. For more information, see "Configuring protected branches."
Enabling force pushes
- On GitHub, navigate to the main page of the repository.
- Under your repository name, click
Settings.

- 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.

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
