Generate Redirects CI: Add a once-daily fallback cron job #121168
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
DilumAluthge
temporarily deployed
to
stopwatch
GitHub Actions
Inactive
|
cc: @jkrumbiegel |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Right now, we only update the redirects when either
Package.tomlis touched or when a manual run is triggered. But GitHub CI jobs sometimes just fails randomly. If the CI job fails whenE/Example/Package.tomlis touched, then the redirect for Example.jl won't get updated until either a manual run is triggered or some other package has theirPackage.tomlfile touched.So, as a fallback, let's rebuild the pages once per day. That way, if the CI job fails when a new package is merged (or an existing package is updated), worst case we have to wait at most 1 day before the redirect is automatically updated.