[WouterVanGoey]

Why:

No issue opened; this is a one-sentence removal.

Since 2025-05-01, draft pull requests are available in all repositories, public or private, on every plan (changelog). The reusable for creating a pull request still tells organization members they "may need to request access to draft pull requests from an organization owner". The section it links to no longer mentions any access requirement. As far as I can tell, no organization setting controls draft pull requests, so the sentence appears to date from when drafts were plan-gated.

What's being changed (if available, include any code snippets, screenshots, or gifs):

Removes one sentence from data/reusables/repositories/create-pull-request.md. The reusable appears on five pages, including "Creating a pull request" and "Creating a pull request from a fork". The link to the "Draft pull requests" section stays.

If an organization-level control over draft pull requests does exist, I'm happy to reword the sentence to name it instead.

Check off the following:

• A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
• The changes in this PR meet the docs fundamentals that are required for all content.
• All CI checks are passing and the changes look good in the review environment.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota.

[github-actions]

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

• Spin up a codespace
• Set up a local development environment

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source	Review	Production	What Changed
code-security/tutorials/fix-reported-vulnerabilities/collaborate-in-a-fork.md	fpt ghec	fpt ghec	from reusable
desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request-from-github-desktop.md	fpt ghec ghes@ 3.22 3.21 3.20 3.19 3.18	fpt ghec ghes@ 3.22 3.21 3.20 3.19 3.18	from reusable
pull-requests/how-tos/create-pull-requests/creating-a-pull-request-from-a-fork.md	fpt ghec ghes@ 3.22 3.21 3.20 3.19 3.18	fpt ghec ghes@ 3.22 3.21 3.20 3.19 3.18	from reusable
pull-requests/how-tos/create-pull-requests/creating-a-pull-request.md	fpt ghec ghes@ 3.22 3.21 3.20 3.19 3.18	fpt ghec ghes@ 3.22 3.21 3.20 3.19 3.18	from reusable

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

[subatoi]

Thanks, @WouterVanGoey; we'll get this reviewed by the appropriate team

[mchammer01]

@WouterVanGoey 👋🏻 - Thanks for catching this and for the clean one-line fix 🙏
You're right, draft pull requests are now available to everyone, so that sentence is outdated.

I'll approve and merge this ⚡

[mchammer01]

Thanks for spotting this inaccuracy and for fixing it ✨

[github-actions]

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡