-
Notifications
You must be signed in to change notification settings - Fork 5
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(surge-deploy): try to limit API rate limit errors #740
Conversation
We currently have rate limit errors when deploying doc PR with surge. Try using the BONITA_CI_PAT to avoid rate limit error
@@ -24,6 +24,7 @@ jobs: | |||
id: surge-preview-tools | |||
with: | |||
surge-token: ${{ secrets.SURGE_TOKEN_DOC }} | |||
github-token: ${{ secrets.BONITA_CI_PAT }} # Avoid rate limiting produced with default GITHUB_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.
thought: The afc163/surge-preview action also do some GH API calls (it does the exact same call as the surge-preview-tools action)
So, it should probably use the PAT.
Notice that this will change the author of PR comment created/updated by the action from github-actions bot to bonita-ci bot. This has no impact for contributors.
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.
It seems better with PAT after some tests on bonita-doc pr
The logic is duplicated from the reusable workflow and so, it must be updated as well
Quality Gate passedIssues Measures |
We currently have rate limit errors when deploying doc PR with surge.
Try using the
BONITA_CI_PAT
instead ofGITHUB_TOKEN
to avoid rate limit error