-
Notifications
You must be signed in to change notification settings - Fork 14
Add a token to avoid rate limits on tests #135
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
Conversation
.github/workflows/tests.yaml
Outdated
| runs-on: ubuntu-24.04 | ||
| env: | ||
| # This is a private access token for @choldgraf that has public read-only access. | ||
| # WARNING: This only works for PRs from non-forked repositories. |
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.
This is not great then, IMO fork based workflow should be encouraged for everyone in general so to remove the "us and them" distinctions between contributors and the core team.
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.
(I don't necessarily say that for this repo as it should be a low traffic utility; but in general for JB)
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.
I agree, I am just trying to get this un-stuck here! The other option would be to re-configure out test suite so that it doesn't hit API rate limits as quickly but that feels like something I don't have the bandwidth to fix right now
|
I've updated this PR so that it will revert to the old behavior if the PR is from a forked repository, that way we'll use the PAT's rate limit for non-forked calls (like releases etc) and we'll use the default github limit for all others. |
|
superceded by #134 |
This cleans up some of our token reading code and un-breaks tests in the process. Here's what this does:
TOKEN_READONLYso that we don't hit rate limits as quickly.