Set CORS headers in 'git' requests so they can be accessed from within pages

[VariantXYZ]

Select Topic Area

Product Feedback

Body

So I've got a project I'm trying to do using GitHub pages that aims to abstract away Git so that translators/editors and people who aren't git experts can contribute to projects directly without needing to worry about git-isms. There's a lot of benefits, but the main reason is that it would allow for using git under the hood to properly track a person's contributions and view translation changesets.

The backbone of this project is the isomorphic-git project, but there's one major issue that prevents me from having an entirely GHP hosted application that does it all... CORS!

As mentioned here:

Unfortunately, due to the same-origin policy by default isomorphic-git can only clone from the same origin as the webpage it is running on. This is terribly inconvenient, as it means for all practical purposes cloning and pushing repos must be done through a proxy.

It'd be great if GitHub repository 'git' protocol requests (through https, at least) would include the necessary access-control entries in the header such that github pages could access them and do a local clone/pull/push via isomorphic git.

My understanding is that just adding the following would be enough:

Access-Control-Allow-Origin: *
Access-Control-Allow-Headers: Content-Type, Authorization

Could GitHub consider making this workflow possible somehow? Or does anyone have a good solution aside from a hosted proxy?