I agree, especially when all you really want to do is make a small change. (I&#x27;m less likely to contribute then - preferring to open an issue and nag someone on the team&#x2F;who already has a fork to implement my one-liner!)<p>But I think it would be look pretty radically different architecturally - where would such a &#x27;push request&#x27; live? You don&#x27;t have push rights on the repo; nor do you have your own fork.<p>It needs to work in a Gitty-way - if not GH would anger far more people than one-line contributors. And Git needs access to a repo to which to push.<p>I suppose a fairly nice solution might be something like:  
- clone  
- edit  
- push --set-upstream origin gh-pr-&lt;my-patch-name&gt;<p>Github could then respond by mocking push-rights for the repo, but really creating a new &#x27;hidden&#x27; repo; and mirroring commits on that branch to a PR opened on the original repo (to which you don&#x27;t actually have anything beyond read-access).<p>When the PR merged they could delete the &#x27;stealth repo&#x27;; of course if you wanted to maintain your own fork it could still work the way in which it does today.