You might want to change the title to match the exact option name

-allow edit by maintainer
+Allow edits from maintainers

I just filed #9921 because I was not able to find this issue before

Moving over feedback from #9921

Personally, I do not see a reason for "Allow edits from maintainers" to have a different behavior if the pull request is coming from a organization. If you think otherwise and it's working as intended then please explicitly state what's the official decision regarding this behavior.

This is blocking some commit-automation-based tools from working as intended, as reported in isaacs/github#1681 (comment)

• feat(codebuild): allow setting concurrent build limit aws/aws-cdk#14099
• Companion for impl Zero and One for fixed point numbers paritytech/polkadot#2922

This is increasingly becoming an issue for pull requests to outside projects from forks inside our Org. I concur with @joao-paulo-parity opinion. If there is a technical limitation causing this option to be missing, we would like an explanation and clearer documentation as to the difference between Org and user created forks in respect to this option's availability.

Is there a simple work around in the meantime? Can commits be added directly to a pull request by the maintainer if they are added to our fork as an outside collaborator? It's not an ideal solution if so, but may help with the issues we are experiencing while making contributions.

This is still an issue.

I use an organization account in order to keep my forked repos separate from my main projects, so I'm always making PRs from an organization account.

There have been several times I wanted to allow edits from maintainers, but was unable to find the option.

WOW -- still an issue.

Anyway -- if it's not going to be changed, then at least put some prominent text on there, so I doin't spend who knows how long looking desperately for the check box!

Maybe, in place of the check box:

"Allowing edits from maintiners is not allows for org accounts' or SOMETHING!!

I also bumped on this after I made a script to clean up my forks

• limitation : modifications allowed by maintainers are not possible ccoVeille/github-forks-sanitizer#3

They have to understand and accept. Some of them decline to join my fork write write permission, but they complain about not being able to push on my fork.

EDIT: For now, I plan to find repositories maintainers via the API, then onboard them on my forks with "write" permission, but it's a pain. after @dluc feedback

So, yes I also need a solution for organization PR

This is still an issue in 2025. Others have pointed out that there are architectural and security reasons why this wouldn't be trivial to do by default for organizations, which is very fair.

However, it would be really nice if this behavior was more clearly signaled on Pull Requests: I have 3-4 conversations a month on Pull Requests where the other maintainer is (reasonably) confused and frustrated because they can't make suggestions or push to my branch, and they typically assume it's a configuration problem (i.e. my fault) instead of GitHub's own limitation.

To that end, even just a small warning on the Pull Request's sidebar explaining that organization forks don't support suggestions or edits from upstream maintainers would go a long way.

Hm interesting. I just crashed into this, and now we need to move our changes from org fork to my for, which takes little bit time, at least when you already create PR already... I mean, is there any solution, on lets say: I have org, we have team and we are using opensource, but, in opensource there is a bug, so our team will create fix (of course in our org fork as it makes sense?) and then what? Somebody then need to manually push that branch to someone's personal fork? I mean... this sounds stupid, or am I stupid?