Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@pwesten had a good idea to run CI on some regular cadence so that we can catch CI bitrot (and Github Actions deprecations) sooner rather than later. This PR creates a simple&naive implementation of this: it schedules CI to run once a week.
Ideally we'd only run this if no other CI has run that week. But that's more work – it'd likely involve hitting Github's API endpoint to determine when the last build was, which isn't super hard (ChatGPT can probably script that pretty quickly), but figured we'd start simple.
Happy to change the cadence, but I already had a repo with a weekly job so I just borrowed that code without much thought.