Repository navigation
Close PRs from organization-owned forks - #3
Merged
Merged
Conversation
GitHub doesn't allow maintainer edits on PRs from forks owned by organizations, even though maintainerCanModify can still report true. Check the head repository owner type and close those PRs with a dedicated message. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
GitHub doesn't allow maintainer edits on PRs from forks owned by organizations, even when "Allow edits by maintainers" is checked. The API can still report
maintainerCanModify: truefor these PRs, so the existing check lets them through, and then maintainers can't push to the branch. This happened on statamic/cms#15982.This adds
__typenameto theheadRepositoryOwnerquery and treats organization-owned forks as uneditable. They get their own comment that explains the organization limitation, since the existing message tells contributors to enable maintainer edits, which they may have already done. PRs fromstatamicbranches are still exempt through the earlier login check.I checked the last 2,000 merged statamic/cms PRs (111 unique authors), and none came from an organization fork other than
statamic, so this wouldn't have closed any of them.Repos that call this workflow pin it to a commit SHA, so the change won't take effect in statamic/cms until a follow-up PR there bumps the pin to this PR's merge commit.