-
-
Notifications
You must be signed in to change notification settings - Fork 204
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
GitHub rate limiting #1006
Comments
Yup, But I'm wondering about a possible integration, maybe simply invoking What do you think? |
Ah, I thought gh auth set the env var. It doesn't - TIL Probably the best would be to do the same thing as gh auth does - grab an oauth token that is scoped appropriately to the needs of git-cliff. It saves dev config time / mistakes. |
I'm not too familiar with that, do you mean an additional |
I meant adding a command that generates the token. It's something I've done a few times for various OAuth things. gh auth login gets a token that's good for the gh cli, not generically for all clis. |
That's something that I should look into for later and I don't think I can include it in the release that I'm preparing soon.
Can you maybe share some examples of that? Do you know any other CLI tools that does something similar? |
The only example I have that I wrote is from a couple of years ago when I first started writing rust, so the code quality isn't really worth considering. The basic technique is
There's quite a few crates that are related. I'm not sure which would be the best to use.
|
Is there an existing issue for this?
Description of the bug
After running git-cliff once for ratatui, and then doing it again shortly after I hit a rate limit. I suspect (but haven't checked) that the github integration parts are not using the logged in github user's context.
Steps To Reproduce
On ratatui main I ran:
Expected behavior
Should not rate limit
Screenshots / Logs
No response
Software information
macos
rust latest
git-cliff 2.7.0
Additional context
No response
The text was updated successfully, but these errors were encountered: