This commit in v6.0.3 released earlier this week on 6/2/2026 I believe I have tracked down to causing API rate limiting related failures starting soon after.
It was discovered by going to our GitHub Organization > Insights > REST API and drilling down into the User and PAT we were using with actions/checkout to checkout other private repositories in our organization. We saw a very high REST requests basically exclusively to /repositories/:repository_id/hash-algorithm. The above commit appears to have newly added these requests.
Would it be possible to make some kind of fix here? Is the request needed? Can it be skipped somehow - preferably automatically/intelligently, but by user input if needed? Or perhaps GitHub doesn't need to count these requests against our API rate limit?
Thank you! Sorry for the quick bug report - hopefully it's not too bad - but I figured getting a report out quickly may help many others in the same boat.
This commit in v6.0.3 released earlier this week on 6/2/2026 I believe I have tracked down to causing API rate limiting related failures starting soon after.
It was discovered by going to our GitHub Organization > Insights > REST API and drilling down into the User and PAT we were using with actions/checkout to checkout other private repositories in our organization. We saw a very high REST requests basically exclusively to /repositories/:repository_id/hash-algorithm. The above commit appears to have newly added these requests.
Would it be possible to make some kind of fix here? Is the request needed? Can it be skipped somehow - preferably automatically/intelligently, but by user input if needed? Or perhaps GitHub doesn't need to count these requests against our API rate limit?
Thank you! Sorry for the quick bug report - hopefully it's not too bad - but I figured getting a report out quickly may help many others in the same boat.