GitHub · Pull requests · Branch protection · Checked October 26, 2026

GitHub: a force push is blocked

A force push is a Git push that overwrites the remote repository with local changes without regard for conflicts. GitHub blocks force pushes on all protected branches by default, and a ruleset's "Block force pushes" rule, enabled by default, prevents users from force pushing to the branches or tags it targets (GitHub's about protected branches and available rules for rulesets, checked October 26, 2026).

{ "type": "non_fast_forward" }
// a ruleset rule: prevent users with push access from force pushing to refs

Where force pushes are blocked

Branch protection: force pushes are blocked on every protected branch unless "Allow force pushes" is selected, under "Rules applied to everyone including administrators". It then lets either everyone with at least write permission force push, admins included, or only the people or teams you specify (GitHub's managing a branch protection rule).
Rulesets: "Block force pushes" applies to the branches or tags the ruleset targets; in the REST API it is the rule non_fast_forward (GitHub's REST API endpoints for rules).
Why GitHub blocks them: a force push may remove from the branch's history commits that other collaborators based their work on, which may lead to merge conflicts or corrupted pull requests. Force pushing can also delete branches or point a branch to commits that were not approved in a pull request.
Other rules still apply: allowing force pushes does not override other rules: if a branch requires a linear commit history, you cannot force push merge commits to it.
The default branch: when a ruleset blocks force pushes, organization owners and repository administrators cannot change or rename the default branch unless they may bypass the ruleset.

When a pull request needs one

Rewritten commits: if an unsigned commit was pushed to a branch that requires commit signatures, GitHub says the collaborator will need to rebase the commit to include a verified signature, then force push the rewritten commit to the branch. On a branch that also blocks force pushes, that last step is refused. Commit metadata rules can likewise call for rewriting commits (see commit metadata rules).
Bringing in the base branch: on the pull request page, "Update branch" merges the base branch into the head branch, and "Update with rebase" rebases your changes onto the latest base branch instead (GitHub's keeping your pull request in sync with the base branch). The REST endpoint "Update a pull request branch" merges the HEAD of the base branch into the pull request branch.

What to do

Find the rule: anyone with read access can view a repository's active rulesets, and in the repository's settings Rules then Insights shows the actions checked against rulesets and, for a failed one, which rules failed (GitHub's managing rulesets for a repository).
Ask to be allowed: with branch protection, an administrator can choose the people or teams who may force push; a ruleset can grant bypass permission to roles, teams or apps (GitHub's creating rulesets for a repository).
Bring in the base branch with a merge: where rebasing the pull request branch would need a force push, "Update branch" (or the REST endpoint) merges the base branch into it instead.

In IntelliJ IDEA: branch protection rules turn off Force Push, rulesets are not loaded

How the Git and GitHub support built into IntelliJ IDEA deal with force pushes to protected branches, in its source (checked November 1, 2026; IntelliJ IDEA: GHProtectedBranchRulesLoader.kt, getProtectionRules.graphql, GithubProjectSettings.kt, GitSharedSettings.java, GitVcsPanel.kt, GitPushSupport.java, ForcePushAction.kt, DvcsBundle.properties, GraphQL files, GithubApiRequests.kt):

Where its protected branches come from: after a successful fetch, if the Git setting "Load branch protection rules from GitHub" is on (it is by default) and the IDE has a GitHub account for that server, the GitHub support asks GitHub for the repository's branch protection rules and keeps only each rule's branch name pattern. These are added to the protected branches in the Git settings, which are master and main by default.
Force Push: when a target branch matches one of those patterns, the Force Push action of the Push dialog is turned off, and its description becomes "Force push to <target> is prohibited", with where to configure protected branches.
What it does not load: from each rule it asks only the pattern, not whether the rule allows force pushes, so a branch whose rule allows them is protected in the IDE too. None of its 78 GraphQL files asks for rulesets, and its list of REST requests has nothing for them, so a branch that only a ruleset protects gets no pattern from GitHub. For a pull request it also fetches the base branch's rule, which includes allowsForcePushes; what the merge check takes from that rule: GitHub: the merge is blocked by unsigned commits.

GitHub pull requests in IntelliJ IDEA

Pull Request Inbox for GitHub, a plugin by Lesstep for JetBrains IDEs 2024.1 or later, shows a pull request's reviews, checks and conversations next to the diff, and merges it with the methods the target branch allows. The plugin does not push or force push: its “Update the branch” uses GitHub's "Update a pull request branch", which merges the base branch into the pull request branch. The review inbox, diffs and conversations are free; approving, commenting, resolving and merging are Pro (US$1.50 a month, with a 30-day trial).

GitHub is a trademark of GitHub, Inc.; IntelliJ IDEA is a trademark of JetBrains s.r.o. This page is not affiliated with or endorsed by GitHub, Inc. or JetBrains.