Maintainers now have more control over how repositories accept contributions. Two new settings let you manage pull requests to better match your project’s needs.
Disable pull requests entirely
You can now turn off pull requests entirely from your repository’s Settings, just like you can with wikis, issues, discussions, and projects. When disabled, the pull requests tab will not be visible. This means no one can see existing pull requests or open new ones.
This is particularly useful for mirror repositories, read-only codebases, or projects where you want to share your work publicly without managing contributions.
Restrict pull requests to collaborators
You can now restrict pull request creation to collaborators only if you still want to use the pull request flow with a managed group of contributors. When enabled, the pull requests tab remains visible. All pull requests can be seen and commented on, but only collaborators (i.e., users with write access) can create new ones. Collaborators can be added or removed by going to the Collaborators tab in a repository’s settings.
This helps you manage contribution quality during critical development phases or when you need tighter control over who submits changes.
Availability
These settings are available now for all public and private repositories. Navigate to your repository’s Settings > General > Features to configure pull request access.
Mobile app: Full UI changes are coming soon to the mobile app. Currently if you disable pull requests, the pull requests tab will still appear in the app, but no one can create new pull requests. All other settings work the same across both platforms.
Note: To temporarily limit activity from certain users on a public repository, you can continue to use temporary interaction limits.
Learn more about managing pull request settings
For a deeper dive on why we’re doing this and our broader efforts, check out our latest blog post. To share your feedback, join the conversation in our Community discussion.