You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
For our enterprise we are facing "API rate limit exceeded ..." errors. I read the documentation how to avoid rate limit issues but for our enterprise using PAT is not feasible. I would like to use the GITHUB-TOKEN for authentication in my Github Workflow since this is the recommended way from GitHub. However, this is not possible at the moment resulting in a Bad Credentials error.
It seems that the AUTH variable variable is not usable in this case since only personal tokens are authenticated with Authorization: token <TOKEN> but for GITHUB-TOKEN one needs to use Authorization: <GITHUB_TOKEN> instead as can be seen in the workflow below in step read limit.
Action version:
4.6.1
Platform:
Ubuntu
Runner type:
Self-hosted
Tools version:
All
Repro steps:
On GHES, following this example I used the following workflow:
Hello @mzwiesler ,
Could you kindly verify if the issue related to the rate limit "API rate limit exceeded ..." has been resolved and confirm that no other issues have emerged while using the setup-actions-demo/setup-python@main branch.
Description:
For our enterprise we are facing "API rate limit exceeded ..." errors. I read the documentation how to avoid rate limit issues but for our enterprise using PAT is not feasible. I would like to use the
GITHUB-TOKEN
for authentication in my Github Workflow since this is the recommended way from GitHub. However, this is not possible at the moment resulting in aBad Credentials
error.It seems that the AUTH variable variable is not usable in this case since only personal tokens are authenticated with
Authorization: token <TOKEN>
but forGITHUB-TOKEN
one needs to useAuthorization: <GITHUB_TOKEN>
instead as can be seen in the workflow below in stepread limit
.Action version:
4.6.1
Platform:
Runner type:
Tools version:
All
Repro steps:
On GHES, following this example I used the following workflow:
Expected behavior:
Installation of python version 3.9.12 and drop of rate limits from 60 to 58.
Actual behavior:
Failure with error
Bad Credentials
.The text was updated successfully, but these errors were encountered: