The articles should have some metadata for the source file within the repo. The problem is as the amount of articles increase, we will be hitting the API request rate limits, which can be seen here. I believe the rates are included in the headers for every request response (here), so for each request, the epoch dates for the rate values can be used to determine when to resume polling
May be a good idea to setup this script up separately, to prevent the build.js from taking even longer. Github Webhook can be used to trigger said job
The articles should have some metadata for the source file within the repo. The problem is as the amount of articles increase, we will be hitting the API request rate limits, which can be seen here. I believe the rates are included in the headers for every request response (here), so for each request, the epoch dates for the rate values can be used to determine when to resume polling
May be a good idea to setup this script up separately, to prevent the build.js from taking even longer. Github Webhook can be used to trigger said job