You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because of CI permissions, if the repo is private then the ci-reporter won't be able to access the service's APIs for the builds. There should be a check in the status event handler to prevent acting on a private repo, which would incur errors.
The text was updated successfully, but these errors were encountered:
Yep! But then I'll need to keep track of the tokens, which means I'll likely need a database to store them, and that's more than I want to do right now. I may have to anyway, CircleCI may always need a token, but if I can avoid a database that'd be nice.
Because of CI permissions, if the repo is private then the ci-reporter won't be able to access the service's APIs for the builds. There should be a check in the status event handler to prevent acting on a private repo, which would incur errors.
The text was updated successfully, but these errors were encountered: