Running CLI fail because of API rate limit in github

From time to time we get an error running the circleci CLI, the reason being that checking the latest release result in “403 API rate limit exeeded”. I can work around the issue by manualy editing ~/.circleci/update_check.yml to a timestamp around current time, but I would rather have a warning message printed instead of terminating the prosess. Also the request is unauthenticated which means you’re limited to 60 req/h. Is there a way to add an oauth token to this request?

Hi @tommybo-entur, setting a GITHUB_TOKEN environment variable should help. We have better handling of this scenario in our backlog. You can find more about this issue here, too.

Apologies for inconvenience!


Worked like a charm. Thanks!

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.