Description
Hey there, after looking at this project a bit I realized it's static, correct?
Was curious if you had an idea of how often this should be built to keep up with a project?
I see that https://expressjs.github.io/statusboard/ hasn't been built in something like 4 months, making some of the information out of date. Meaning I clicked through a couple "help wanted" issues which were already closed. (obviously that wasn't so much on purpose but just because this is a WIP)
After thinking about it I realized I don't know how often I'd expect this type of project to be rebuilt.
My first instinct was maybe it should be dynamic then, to keep up to date. But that gets into rate limiting on the GH api, as well as auth'd API calls for non-public projects.
I am likely just overthinking this, a new build on each issue open/close or label change might not be a huge deal. But it does seem inefficient.
I think efficiency talk is a bit too early of optimization here and instead a better question would be:
what level of detail and up to date-ness should this type of project aspire to?
What do you have in mind as the role this could serve for projects like express or others? I've found it useful already for express, where it was up to date.
Edit: Ahh I see now it's not exactly static! I need to dig into the code more I suppose, I just noticed there are requests happening to a json file to get the data. Updating those json files would definitely be more lightweight than doing a full build.