fix: run requirements cron job on even weeks only #48
Conversation
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
See an example of a skipped job for an odd week here: https://github.com/ComPWA/ampform/actions/runs/1778324274
This was referenced Feb 1, 2022
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.
bb3a47f introduced a bug: it lets the requirements upgrade cron job on every other week, but starting on the first day of each month. The result is that the weekday on which the cron job runs switches each month. For certain months, this can also result in redundant pull requests like ComPWA/qrules#148, ComPWA/ampform#223, and ComPWA/tensorwaves#408. (They have been modified to include the fix by this repo-maintenance PR.)
https://github.com/ComPWA/ampform/actions/runs/1778324274
https://github.com/ComPWA/ampform/actions/runs/1778340043