This is a new, improved version of https://github.com/awesome-selfhosted/awesome-selfhosted/
Please check the release announcement for more details.
Maintainer here, happy to answer questions.
This is a new, improved version of https://github.com/awesome-selfhosted/awesome-selfhosted/
Please check the release announcement for more details.
Maintainer here, happy to answer questions.
Couldnt agree more! This is why I decided not to use discussions or issue count since those are GitHub specific. Commit count could be gathered from any platform that uses git.
Im using the GitHub GraphQL API to query all necessary information for 100 repos at a time, including commit count per month. The rate limit for GraphQL is allowing up to 5000 points per hour and on of these queries only costs 1 point. Herre is my code to generate the query: https://github.com/mkitzmann/awwesome/blob/main/src/lib/query.ts
The Informationen is currently just „{month: count,…}“, so should be fairly simple to store in yml. I will create an issue for it.
When using the automatic
GITHUB_TOKEN
created for each GH actions workflow, the limit is only 1000 requests per hour [1]. The list has 1080 projects whose source is hosted on github, and we must do 2 API calls for each one because for some reason the date of last commit to the default branch is not available directly from the repos API endpoint [2] (do not trustupdated_at/pushed_at
, it’s a lie). So we currently have to add a sleep of ~7 seconds between each API call to not hit the rate limit for the metadata update job that runs daily.The limit of 5000 requests/hour only applies to personal access tokens which have far too many permissions on my personal account to be used in a shared/community project.
Someone in https://old.reddit.com/r/selfhosted/comments/15y7y36 mentioned https://analyzemyrepo.com/analyze/inventree/InvenTree which may be interesting to integrate somehow.