The "DESCRIPTION" section of ads-github-show-rate-limits(1) says:
The program makes an authenticated HTTP 'HEAD' call to the GitHub API
(using curl(1)) to obtain the HTTP response headers that contain the
service rate limit information. The rate limit information is parsed
out of the headers and presented to the user.
While per-endpoint calls do allow for the possibility of extracting GitHub
service limit information out of the HTTP response headers (e.g., see the
"Rate Limiting" section of the GitHub API documentation),
the 'ads-github-tools-show-rate-limits' program is actually making a call to
the GitHub /rate_limit API endpoint and extracting the
data that it displays out of the JSON returned in the HTTP response body.
The documentation should be updated to correct this point.
The "DESCRIPTION" section of
ads-github-show-rate-limits(1)says:While per-endpoint calls do allow for the possibility of extracting GitHub
service limit information out of the HTTP response headers (e.g., see the
"Rate Limiting" section of the GitHub API documentation),
the
'ads-github-tools-show-rate-limits'program is actually making a call tothe GitHub /rate_limit API endpoint and extracting the
data that it displays out of the JSON returned in the HTTP response body.
The documentation should be updated to correct this point.