-
-
Notifications
You must be signed in to change notification settings - Fork 26
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
Use GHA's token #310
base: main
Are you sure you want to change the base?
Use GHA's token #310
Conversation
Oh, the script needs a username. I'll think on this. |
Ok, so the GITHUB_TOKEN is for a builtin github app, not your own account, so that i.e., contributing to a project with extensive doesn't use up your personal rate. Thus, there's not a username associated with it. However, I think we don't need a username to make authenticated requests, do we? Could we make it optional? |
GHA provides a token itself, we don't need to generate one. This is more-fine grained, easier to change if needed, and more secure. I think the existing `contents: read` is sufficient, but it might not be. We'll see.
4ab0b6d
to
3cb829d
Compare
Hmm, looks like it's not picking up AUTH_GITHUB. |
It's worth noting that the workflow token is only 1000 requests per hour, whereas a pat is 5000, so this is only helpful if we've got over 5 pushers an hour. EDIT: So there's some useful stuff in here, but using gha's token doesn't help. |
4d17f16
to
1f6fd01
Compare
* Don't tell authenticated users to log in. * Tell users when the rate limit expires.
1f6fd01
to
993a0ed
Compare
GHA provides a token itself, we don't need to generate one. This is more-fine grained, easier to change if needed, and more secure.
I think the existing
contents: read
is sufficient, but it might not be. We'll see.Based on #309 (comment).