New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: set GITHUB_ACCESS_TOKEN to temporary read only token #1612
ci: set GITHUB_ACCESS_TOKEN to temporary read only token #1612
Conversation
The token provided by secrets.github_token in github workflows does not have permissions to work against the api.github.com/gists endpoint.
9b36832
to
44260da
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. Not merging yet to see what others think.
I started looking last night, saw a massive JSON blob.... and decided to leave it 😄. Everything else looked fine though, so happy to go with @betatim |
Ah sorry about the JSON blob. I wrote about it but then felt my PR description ended up so long that it was boring to read through and removed my notes about it ^^ The JSON changes is two keys representing api.github.com/gists URLs that are to be mocked that I relocated from one file to a standalone file. In other words, its just one file split in two. Thanks for reviewing this, I'll go for a merge! |
jupyterhub/binderhub#1612 Merge pull request #1612 from consideRatio/pr/attempt-fix-github-ratelimit
I spotted a typo in this PR so the issue wasn't resolved. I added a commit fixing that typo in #1615 now though. |
We ran into rate limitations, but by setting the env var
GITHUB_ACCESS_TOKEN
in our GitHub Job's, which is the default value forc.GitHubRepoProvider.access_token
, this is no longer an issue.We still have to mock tests with GistRepoProvider as the
secrets.github_token
is not provided rights to access api.github.com/gists.Remaining test failure is resolved by #1615