5 ms·

We definitely plan on getting a domain once the hackathon is over and we have some time to relax and really plan this out :) As I mentioned earlier, you have n

We definitely plan on getting a domain once the hackathon is over and we have some time to relax and really plan this out :) As I mentioned earlier, you have nothing to worry about - we don't touch your repos! Unfortunately the read permissions we need are classified as "write" (or at least we couldn't find a way to specify them as "read" in our very limited time). Once everything settles down we are going to think about ways to make it easier for people to use and trust the service so that they don't need to worry about permissions or anything like that. Thanks so much for your input, we'll definitely take it into account!

pbiggar 13y ago
> or at least we couldn't find a way to specify them as "read" in our very limited time You didn't miss anything - GitHub repo permissions are pretty much all-or-nothing. We've been putting up with this for two years at CircleCI :( [For others, to read from a private repo, you need to request the "repo" scope, which actually gives read+write access to every repo in every org that you have access to. See https://circleci.com/docs/github-permissions https://circleci.com/docs/github-permissions for more details.]