feat: Add pull request settings to github_repository

[nicolas-grekas]

Resolves #3198

---

Before the change?

github_repository could 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 the github_repository data source):

• has_pull_requests (bool, defaults to true) — set to false to disable pull requests on the repository.
• pull_request_creation_policy (all / collaborators_only) — restricts who can open pull requests.

has_pull_requests defaults to true so existing repositories keep pull requests enabled rather than being silently disabled on the next apply. pull_request_creation_policy is only sent when pull requests are enabled, mirroring how the existing merge_commit_* / squash_merge_commit_* arguments are gated on their parent toggle.

Important

Blocked on a go-github release. The struct fields land in google/go-github#4268, which merged after v88.0.0. go.mod currently pins a master pseudo-version so the code compiles; it must be repointed to the eventual v89 release before this can merge. This matches the issue's existing Blocked status.

Pull request checklist

• Schema migrations have been created if needed (none needed — additive optional fields)
• Tests for the changes have been added (for bug fixes / features)
• Docs have been reviewed and added / updated if needed (for bug fixes / features)

Does this introduce a breaking change?

• Yes
• No

---

[github-actions]

👋 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.}