Closed victorlin closed 5 months ago
@jameshadfield good point. All the testing operations are read-only, so the restricted access should be sufficient. Since this is the only usage of GITHUB_TOKEN
in this repo's CI, I've updated it to be restricted in the repo settings.
Rebased onto latest master
which should fix the issue with aws-region.
The org-wide change is to store AWS_REGION
in an organization variable instead of per-repo secrets.
Description of proposed changes
Previously, the unauthenticated requests were limited to 60 per hour per IP address which are likely shared by other jobs using the same GitHub-hosted runners.
Related issue(s)
Prompted by https://github.com/nextstrain/nextstrain.org/pull/810#discussion_r1556421873
Checklist
GITHUB_TOKEN