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
docs(configuration options): Add a CodePen for validating whether a later.js schedule is valid or not. #16431
Conversation
One challenge here - Renovate accepts only a subset of Later.js schedules. For example the default "every 5 minutes" is not a valid Renovate schedule. Can this codepen be made to mimic what Renovate considers valid? |
@rarkins No promises but happy to take a look at modifying it! Any pointers on where in the codebase should I look for that Renovate-flavored Later.js? Happy to look myself, but appreciate any points in the right direction! |
Co-authored-by: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com>
Co-authored-by: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com>
Awesome will take a look |
Co-authored-by: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com>
Alright, updated with the rules - take a look: https://codepen.io/rationaltiger24/pen/ZExQEgK I do have a question through. For example, running "on Monday before 3am" with the date as 2022-07-07 with a local time in Chicago (UTC-5), will return the next two occurrences as: 7/11/2022, 12:00:00 AM By I assume Rennovate would not run every minute under this configuration? Or am I missing something? |
That's right. Schedules do not trigger Renovate to run. Instead, if Renovate is running AND the schedule matches at that time, then it will create branches/PRs. |
That makes sense, but what triggers Renovate to run, assuming it is a GitHub app that is installed |
It tries to run hourly by default and reduces cycles if no activity on repo. You can always trigger a run from dependency dashboard. |
Perfect that makes sense to me! |
🎉 This PR is included in version 32.108.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Changes
Context
I think for individuals who aren't familiar with later.js (like me!), it can be difficult to tell whether a
schedule
is valid. Plus, I found their documentation was missing some sort of "demo" feature. Hence, I made a quick CodePen to validate whether the proposed schedule is valid. It also lists the next two occurences in that schedule. I found this very helpful in reaching an intuitive understanding of how the schedules worked, and it may be helpful to other users as well.Documentation (please check one with an [x])
How I've tested my work (please tick one)
I have verified these changes via: