-
Notifications
You must be signed in to change notification settings - Fork 276
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
Docs - Add faq for github rate limit #646
Conversation
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.
Thanks for adding this @sangee2004!
Left a suggestion. LMK what you think.
cdb0076
to
26f271e
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.
Just one formatting nit, but other than that, LGTM!
docs/docs/09-faqs.md
Outdated
If you're already authenticated with the `gh` CLI, you can use its token by running: | ||
```bash | ||
export GITHUB_AUTH_TOKEN="$(gh auth token)" | ||
``` |
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.
If you're already authenticated with the `gh` CLI, you can use its token by running: | |
```bash | |
export GITHUB_AUTH_TOKEN="$(gh auth token)" | |
``` | |
If you're already authenticated with the `gh` CLI, you can use its token by running: | |
```bash | |
export GITHUB_AUTH_TOKEN="$(gh auth token)" |
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.
LGTM as well, pending that nit
26f271e
to
1b68119
Compare
Added workaround that can be done when gptscript execution results in github rate limit errors in FAQ section.