Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Github CORS requirement clarification
See original GitHub issueI’ve been asking Github to enable CORS headers to their HTTPS git servers, but they’ve refused to do it. This means that a browser can never clone from github because the browser will disallow XHR requests to the domain. They do, however, offer a REST interface to the raw git data. Using this I wrote a mixin for js-git that uses github as the backend store.
I am trying to understand if the lack of CORS support is limiting, if you are able to use the raw git data API. I guess this just necessitates the js-github adapter as opposed to using the normal git communication mechanisms. is it otherwise feature complete? Does this include pushing commits back to github?
Issue Analytics
- State:
- Created 9 years ago
- Comments:12 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
As far as I know, they never responded. The joys of putting all our open source ecosystem in the hands of a closed-source company. Maybe we should reach out again now that they are part of Microsoft? Anyone have good contacts there?
Credentials would be needed for private repos or pushing changes. But currently I can’t even read public repos without CORS enabled on their end.