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
This could quickly deplete the number of allowed requests to the API, which is 5000 requests/hour for personal user tokens, and only 1000 requests/hour for Github Actions temporary GITHUB_TOKEN[1] (which is already a probelm in https://github.com/awesome-selfhosted/awesome-selfhosted-data for which we must already wait 7.3 seconds between each call to avoid reaching the rate limit [1]).
However, disabling querying this information during daily/automatic updates, and manually triggering it with a long wait_time from time to time remains a possibility.
The text was updated successfully, but these errors were encountered:
Ref. awesome-selfhosted/awesome-selfhosted-data#35
This information is not directly available from the repository API endpoint, it seems the contributors endpoint must be queried and the
length
of the returned list must be computed - if the number of contributors is greater than 100, multiple queries must be done, and the length of each page must be summed to get the total number of contributors until an empty page is returned (https://stackoverflow.com/questions/49209146/how-to-find-number-of-contributors-for-a-repository).This could quickly deplete the number of allowed requests to the API, which is 5000 requests/hour for personal user tokens, and only 1000 requests/hour for Github Actions temporary
GITHUB_TOKEN
[1] (which is already a probelm in https://github.com/awesome-selfhosted/awesome-selfhosted-data for which we must already wait 7.3 seconds between each call to avoid reaching the rate limit [1]).However, disabling querying this information during daily/automatic updates, and manually triggering it with a long
wait_time
from time to time remains a possibility.The text was updated successfully, but these errors were encountered: