[hugovk]

Why:

The original "configured after" made is sound like changing a setting later in time meant it took precedence.

After testing, I've confirmed that repo-level takes precedence over org-level, and chronology has nothing to do with it.

Let'd clarify the ambiguous docs.

Closes: #46516

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

Clarify repo limits override org limits.

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.

[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
communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md	fpt ghec	fpt ghec

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

🤖 This comment is automatically generated.

[Copilot]

🟡 Changes recommended

The phrase “every repository” overstates the setting’s scope, which is limited to public repositories owned by the organization.

1 open issue

• Clarify repository scope to public repositories · New

What changed in this PR

Clarifies GitHub Docs guidance on pull request limit precedence, addressing the ambiguity reported in #46516.

Changes:

• Explains that organization-level limits apply when a repository has no limit of its own.
• States that repository-level limits override organization-level limits without implying that configuration timing matters.

File	Description
content/​communities/​moderating-comments-and-conversations/​limiting-interactions-in-your-organization.md	Rewords pull request limit precedence to remove chronological ambiguity.

_{Review effort: Max}

[subatoi]

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