GitHub: pull requests cannot be opened in this repository
A repository can turn pull requests off entirely, or let only collaborators create them (GitHub's disabling pull requests, checked October 27, 2026). A public repository can also limit for a while who may create pull requests, and cap how many pull requests people without write access may have open at the same time (GitHub's limiting interactions in your repository).
turned off Settings, Features: Pull requests deselected collaborators only Settings, Features: Pull requests, Collaborators only interaction limit public repositories, 24 hours to 6 months open pull request limit public repositories, people without write access REST has_pull_requests, pull_request_creation_policy
Why it is refused
- Turned off: under Features in the repository's Settings, Pull requests is deselected. GitHub's documentation says that if pull requests are turned on again later, the pull requests added before are available.
- Collaborators only: the dropdown under Pull requests is set to Collaborators only. In a repository owned by a personal account, a collaborator is anyone who has been invited to the repository; in an organization's repository, a user with the write, maintain or admin role.
- An interaction limit: on a public repository, a temporary limit of 24 hours, 3 days, 1 week, 1 month or 6 months stops certain users from creating pull requests, commenting, opening issues and more. By type, it limits accounts less than 24 hours old without prior contributions, users who have not contributed to the default branch before, or users without write access. A limit set for the whole personal account or organization covers all its repositories (GitHub's temporary interaction limits). For comments, see comment or reply refused.
- The open pull request limit: in a public repository, a user without write access can have only a set number of pull requests open at the same time, drafts included when the repository counts them. At the limit, an existing pull request has to be closed or merged before a new one can be opened. Users with write access are not affected, and up to 100 users on the bypass list may exceed it (GitHub's limiting concurrent open pull requests).
Reading and changing the setting
- Read: GET /repos/OWNER/REPO answers has_pull_requests and pull_request_creation_policy, which is all or collaborators_only (GitHub's get a repository).
- Change: PATCH /repos/OWNER/REPO with has_pull_requests true to allow pull requests or false to prevent them, and pull_request_creation_policy all or collaborators_only (GitHub's update a repository).
- The limits: in Settings, under Moderation options, Interaction limits holds both the temporary interaction limits and, under Pull request limits, the maximum, whether drafts count, and the bypass list (GitHub's configuring the pull request limit).
What to do
- Turned off: ask the maintainers how the project takes changes; they can select Pull requests under Features again.
- Collaborators only: ask to be invited as a collaborator, or for a collaborator to open the pull request.
- An interaction limit: after the duration passes, users can resume normal activity in the repository.
- The open pull request limit: close one of your open pull requests, or wait until one is merged; maintainers can add regular contributors to the bypass list instead of giving them collaborator access.
- Abuse from strangers: GitHub's documentation asks you to contact GitHub Support if you want to turn off pull requests because of abuse from strangers.
GitHub pull requests in IntelliJ IDEA
Pull Request Inbox for GitHub, a plugin by Lesstep for JetBrains IDEs 2024.1 or later, creates a pull request from the branch you have checked out, into a target branch it offers from the repository's branches on GitHub. When pull requests are turned off for the repository, it says so before the dialog opens, as none can be created there; when only collaborators can create them, the dialog says so. When GitHub refuses to create it, the plugin shows GitHub's answer. It shows a pull request's reviews, checks and conversations next to the diff. The review inbox, diffs and conversations are free; creating pull requests, 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.
More: GitHub merge refused (405, 409) · GitHub review refused (422) · GitHub search 422 "Validation Failed" · "Resource not accessible by personal access token" · 401 "Bad credentials" · "Resource protected by organization SAML enforcement" · "API rate limit exceeded" · GitHub diff 406 "too_large", 3,000 files · GitHub line comment 422 "must be part of the diff" · GitHub branch update refused (422) · GitHub pull request not created (422, 403) · GitHub auto-merge refused · GitHub draft, ready for review or close refused · GitHub conversation not resolved · GitHub checks not shown (check runs 403) · GitHub file contents not read · GitHub compare refused (404, 422) · GitHub comment or reply refused (403 locked, archived) · GitHub merge method not allowed (405) · GitHub branch not found (404, 301) · GitHub Enterprise Server not reached · GitHub review request not shown · GitHub pull request list incomplete · GitHub 404 Not Found, renamed repositories (301, 307) · GitHub line comment outdated or not on the diff · GitHub pull requests not updating, notifications late · GitHub suggested change cannot be applied · GitHub required check stuck at "Expected" · GitHub code owner review required · GitHub merge blocked by unresolved conversations · GitHub merge blocked by unsigned commits · GitHub branch that merges through a merge queue · GitHub merge waiting for an approval of the most recent push · GitHub merge waiting for code scanning results · GitHub merge waiting for code quality results · GitHub merge blocked by a code coverage threshold · GitHub merge blocked by license compliance results · GitHub branch locked or its updates restricted · GitHub branch not deleted after merging · GitHub merge waiting for a team's approval (Required reviewers) · GitHub merge blocked by secret scanning alerts · GitHub stacked pull request not merging · GitHub push blocked by push rules · GitHub merge blocked by commit metadata rules · GitHub force push blocked · GitHub issue not closed by a merged pull request · GitHub pull request not checked out locally · GitHub pull request has merge conflicts · GitHub changes requested and dismissing a review · GitHub co-author not credited for a commit · GitHub dependency review check failed · GitHub Dependabot not rebasing its pull request · GitHub fork not syncing with upstream · GitHub pull request base branch not changing · GitHub pull request not reverting · GitHub pull request template not showing · GitHub pull request labels or assignees not added · GitHub pull request not closing or reopening · GitHub push blocked by push protection · GitHub pull request comment hidden · GitHub pull request blocked until deployments succeed · GitHub team review request replaced by members · GitHub pull request file no longer marked Viewed · GitHub pull request marked merged without being merged · GitHub Copilot review does not count as an approval · GitHub checks not running on a pull request a workflow created · GitHub Update branch button not shown on a pull request · GitHub checks failing on a Dependabot pull request · GitHub checks failing on a pull request from a fork · GitHub checks skipped by [skip ci] in a commit message · GitHub checks gone after the retention period · GitHub code review limits in a public repository · GitHub checks run on every pull request in a stack · GitHub pull request showing commits already squash merged · GitHub pull request not showing a file diff · GitHub push to a pull request branch from a fork refused · GitHub check cancelled on a pull request · GitHub Rebase and merge not available · GitHub merge commit message not what you expected · GitHub pull request shows every line changed · GitHub API request timed out · GitHub pull request image or document diff not shown · GitHub review request refused (422) · GitHub pull request from Copilot: checks not running, approval not counted · GitHub push refused: GH006 and GH013 on a protected branch · GitHub "At least 1 approving review is required", approvals that do not count · GitHub pull request plugins for IntelliJ IDEA, compared · 日本語