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:
Runner type:
Tools version:
All
Repro steps:
On GHES, following this example I used the following workflow:
name: CI With GitHub Token
on: [workflow_dispatch]
jobs:
sample_build:
runs-on: [azure-runners]
steps:
- name: "rate limit"
run: |
curl \
-H "Accept: application/vnd.github.v3+json" \
-H "Authorization: $TOKEN" \
https://api.github.com/rate_limit
env:
TOKEN: ${{ secrets.GITHUB_TOKEN }}
- name: Clear the tool cache
run: rm -rf /Users/runner/hostedtoolcache/Python/
- name: Set up Python
uses: actions/setup-python@v4.6.1
with:
token: ${{ secrets.GITHUB_TOKEN }}
python-version: 3.9.12
- name: "rate limit"
run: |
curl \
-H "Accept: application/vnd.github.v3+json" \
-H "Authorization: $TOKEN" \
https://api.github.com/rate_limit
env:
TOKEN: ${{ secrets.GITHUB_TOKEN }}
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.
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-TOKENfor authentication in my Github Workflow since this is the recommended way from GitHub. However, this is not possible at the moment resulting in aBad Credentialserror.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-TOKENone 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.