CI Add cron schedule for lock-file workflow#27732
Merged
betatim merged 1 commit intoscikit-learn:mainfrom Nov 6, 2023
Merged
Conversation
glemaitre
approved these changes
Nov 6, 2023
betatim
approved these changes
Nov 6, 2023
Member
Author
|
Nice, let's see what happens next Monday! |
REDVM
pushed a commit
to REDVM/scikit-learn
that referenced
this pull request
Nov 16, 2023
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
I ran manually the lock-file bot actions twice and it seems to have worked fine, see action runs and created PRs. The first run with failure was due to scikit-learn-bot permissions, see #27622 (comment) for more details.
I used a weekly cron job that runs every Monday at 5am (see this for double-checking the cron syntax). If we want to run it less often, we could run it every 1st and 15th of the month (there is no easy way to do every two weeks with cron)
I left the workflow_dispatch that can still be handy to trigger manually the workflow in some cases where we don't want to wait for the next scheduled job.