The GitHub REST API Search endpoint, when searching for repositories, returns a lot more data than expected.
We don't actually need to make more requests to get back the Respository Topics or create date.
Using the data from the search result totally removes the need to do requests per repo.
This does require quite a change to the code, and attempting to modify such might want to wait till #10 is merged, or that PR might not even be needed now.
For the json-schema topic on Github (like a "tag" for repos, but tags are something else, so I guess they picked another word), there are under 2k results, and you can request 1k results per query with the search API. The response contains all the initial data required.
Currently we aimed to have both the created at date and the first release date, but let's forgoe having the first release date, as that makes this more complicated, and we probably don't even need it.
The GitHub REST API Search endpoint, when searching for repositories, returns a lot more data than expected.
We don't actually need to make more requests to get back the Respository Topics or create date.
Using the data from the search result totally removes the need to do requests per repo.
This does require quite a change to the code, and attempting to modify such might want to wait till #10 is merged, or that PR might not even be needed now.
For the
json-schematopic on Github (like a "tag" for repos, but tags are something else, so I guess they picked another word), there are under 2k results, and you can request 1k results per query with the search API. The response contains all the initial data required.Currently we aimed to have both the created at date and the first release date, but let's forgoe having the first release date, as that makes this more complicated, and we probably don't even need it.