-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Try to fix Lychee github action error #1034
Conversation
6ae9346
to
93e07a7
Compare
Deploying docs with Cloudflare Pages
|
f896b96
to
ce5243b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The reason I think we should accept 429 responses is to clean up GitHub's rate limiting errors from the reports. We pass in a token and that should be giving us 1000 requests and hour but with the number of commits we push and number of links we have it seems to be hitting the ceiling.
In addition, I think we should convert this to a cron job that we run, say, monthly? It's going to file github issues when there's an issue (and it already has filed several from your tests).
e697e7e
to
f03d8cc
Compare
Discussed offline, we need to merge this so we can see if the crontab works tomorrow!
This fixes the Lychee GitHub action so it doesn't fail on each PR
main
using a cron schedule, for 12:01 AM on the 1st of each month