feat: Add pull request settings to github_repository - #3479
Open
nicolas-grekas wants to merge 1 commit into
Open
feat: Add pull request settings to github_repository#3479nicolas-grekas wants to merge 1 commit into
nicolas-grekas wants to merge 1 commit into
Conversation
|
👋 Hi, and thank you for this contribution! This repo is maintained by GitHub and community members on a best-effort basis. We'll get to this as soon as we can. You can help us prioritize by joining the discussion on open issues and PRs, sharing details on the changes you need, and reviewing other contributions. 🤖 This is an automated message. |
|
@nicolas-grekas v89 just released! |
1 task
5 tasks
|
hi @nicolas-grekas, is there any chance you can pick this back up? |
nicolas-grekas
force-pushed
the
feat/repository-pull-request-settings
branch
from
August 10, 2026 07:34
dfbe700 to
d457d80
Compare
GitHub added two repository settings in February 2026: disabling pull requests entirely (has_pull_requests) and restricting who can open them (pull_request_creation_policy, "all" or "collaborators_only"). has_pull_requests defaults to true so existing repositories keep pull requests enabled. The creation policy is only sent when pull requests are enabled, matching how the merge-commit title/message fields are handled.
nicolas-grekas
force-pushed
the
feat/repository-pull-request-settings
branch
from
August 10, 2026 07:48
d457d80 to
6896fe0
Compare
nicolas-grekas
marked this pull request as ready for review
August 10, 2026 07:50
Author
|
thanks for the reminder, this is now ready for review! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resolves #3198
Before the change?
github_repositorycould not manage the repository pull request settings GitHub shipped in February 2026: disabling pull requests entirely, and restricting who can open them.After the change?
Two new arguments on
github_repository(and read-only attributes on thegithub_repositorydata source):has_pull_requests(bool, defaults totrue) — set tofalseto disable pull requests on the repository.pull_request_creation_policy(all/collaborators_only) — restricts who can open pull requests.has_pull_requestsdefaults totrueso existing repositories keep pull requests enabled rather than being silently disabled on the next apply.pull_request_creation_policyis only sent when pull requests are enabled, mirroring how the existingmerge_commit_*/squash_merge_commit_*arguments are gated on their parent toggle.The struct fields landed in google/go-github#4268, released in
v89.0.0, whichmainalready depends on — so this is no longer blocked.Pull request checklist
Does this introduce a breaking change?