3 ms·

(github login required, but worth it!)

• chillitom 13y ago
  Why is it asking for permission to "Update your public repositories (Commits, Issues, etc)."?
  • jlarocco 13y ago
    This was was linked to, I think indirectly, a week or two ago. I asked the same thing there, and the reply I got was that it's required because it's a "beta" version of the book and they want reviewers to open issues/pull requests when problems are found. It's an interesting idea, but there's no way I'm giving a stranger write access to my GitHub account.
  • untothebreach 13y ago
    If you look at the FAQ, they go over the reason for that: > Sadly, the Github oAuth mechanism is severely > limited in how much access control that we can request. > We just want the ability to create issues in one specific > public repository, but the minimum privileges we can > request from Github are the ones you see when you login. > If you can convince someone at Github to add more > granular permissions, let us know! However, we never > store your authorization tokens in our server, and > instead just directly pass your authorization token into > a client-side cookie. http://www.realworldocaml.org/#faq http://www.realworldocaml.org/#faq