Add GitHub API authentication to avoid rate limit errors #23
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
The script makes unauthenticated requests to the GitHub API, which causes 403 rate limit errors when running frequently in CI/CD:
Example: https://github.com/CaddyBuilds/caddy-cloudflare/actions/runs/18362086185
Unauthenticated requests are limited to 60/hour, while authenticated requests get 5,000/hour.
Solution
Added support for the
GITHUB_TOKEN
environment variable to authenticate requests. The script falls back gracefully to unauthenticated requests if the token is not provided.Usage
In GitHub Actions workflows:
The
GITHUB_TOKEN
is automatically provided by GitHub Actions and requires no additional configuration.Changes
GITHUB_TOKEN
from environmentAuthorization
header when token is availableThis is fully backward compatible and eliminates rate limit issues.