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
some scripts depend on the github API (the one I had a problem with was dotnet/install_ddtrace.sh, which queries the API to get the latest version of the tracer), and when using them from a shared location (like the office), it's very easy to hit the rate limits, which in my case prevented me from rebuilding the image.
We could let users use the authenticated API instead, which has higher limits (and per-user limits instead of per-IP). They could do that by setting an env variable GITHUB_TOKEN, that'd have to be passed to docker, and used in the curl headers when necessary (and only if present, to avoid breaking everyone's workflow).
See https://docs.github.com/en/rest/authentication/authenticating-to-the-rest-api
The text was updated successfully, but these errors were encountered:
some scripts depend on the github API (the one I had a problem with was
dotnet/install_ddtrace.sh
, which queries the API to get the latest version of the tracer), and when using them from a shared location (like the office), it's very easy to hit the rate limits, which in my case prevented me from rebuilding the image.We could let users use the authenticated API instead, which has higher limits (and per-user limits instead of per-IP). They could do that by setting an env variable
GITHUB_TOKEN
, that'd have to be passed to docker, and used in the curl headers when necessary (and only if present, to avoid breaking everyone's workflow).See https://docs.github.com/en/rest/authentication/authenticating-to-the-rest-api
The text was updated successfully, but these errors were encountered: