GitHub · Pull requests · Push rulesets · Checked October 26, 2026

GitHub: a push is blocked by push rules

Push rulesets block pushes to a private or internal repository, and to that repository's entire fork network, based on file paths, file path lengths, file extensions and file sizes. Push rules do not target branches: they apply to every push to the repository. A commit that breaks one of them cannot be pushed, so it does not reach GitHub, and no pull request can include it until the commits are changed (GitHub's about rulesets, checked October 26, 2026).

"target": "push",
"rules": [ { "type": "max_file_size", "parameters": { "max_file_size": 10 } },
           { "type": "file_path_restriction",
             "parameters": { "restricted_file_paths": ["test/demo/**/*"] } } ]

The four push rules

Restrict file paths: commits that include changes in the listed paths cannot be pushed. Paths use fnmatch syntax: test/demo/**/* blocks everything in test/demo/, and test/docs/pushrules.md blocks that one file. Up to 200 entries of up to 200 characters each (GitHub's available rules for rulesets).
Restrict file path length: commits that include a file path longer than the set number of characters cannot be pushed.
Restrict file extensions: commits that include files with the listed extensions cannot be pushed. Up to 200 entries of up to 200 characters each.
Restrict file size: commits with a file over the set size cannot be pushed. In the REST API the limit is given in megabytes, from 1 to 100, and it does not apply to Git Large File Storage (GitHub's REST API endpoints for rules).

Where they apply

The whole fork network: a fork of a repository with push rulesets gets the same push rules, and for a fork, only the people who may bypass a push rule in the root repository may bypass it.
Some REST API endpoints too: push rulesets apply to "Create a blob", "Create a tree" and "Create or update file contents" (GitHub's troubleshooting rules).
Large pushes: with push rulesets, a push may update at most 1,000 references; a push over that limit is rejected.
Which repositories: push rulesets can be created for private and internal repositories.

What to do

Change the commits: the rules judge the commits being pushed ("commits that include changes in specified file paths" and so on), so the commits that are not on GitHub yet have to be changed until none of them breaks a rule. GitHub's troubleshooting says that, depending on the rules, you may need to edit your commit history locally before you can push, for example with an interactive rebase.
Check the allowed exceptions: "Restrict file paths" and "Restrict file size" can list allowed exceptions in fnmatch syntax, such as **/gradle/wrapper/*.jar. A repository, organization or enterprise administrator can add one for a file that must stay pushable. Only these two rules support allowed exceptions; for one file of an otherwise blocked file type, GitHub points to "Restrict file paths" with a pattern such as **/*.jar.
Find the rule: anyone with read access can view a repository's active rulesets. In the repository's settings, Rules then Insights shows the actions checked against rulesets, the ones that failed, and, for a failed one, which rules failed (GitHub's managing rulesets for a repository). The same insights are in the REST API for rule suites.
A large file the project needs: the file size limit does not apply to Git Large File Storage.

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 commits itself: when you create a pull request from a branch that is not on GitHub yet, it says so and offers the IDE's Push dialog, where a push these rules refuse fails. 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.