Fail on unparseable scheduled dates#245
Open
AndreaGriffiths11 wants to merge 2 commits into
Open
Conversation
Scheduled issues with unsupported date formats were being skipped while the workflow still passed. Raising an explicit error makes the schedule update fail when a scheduled stream cannot be represented in the README. Co-authored-by: Copilot <[email protected]>
Co-authored-by: Copilot <[email protected]>
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
1 participant
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.
What
Raise an explicit error when a scheduled issue has a date value that
update_schedule.pycannot parse.Why
Scheduled issues should not disappear from the README schedule while the workflow still reports success. If the date format is unsupported, the schedule update should fail so the issue can be corrected.
Verification
update_schedule.pylocally and confirmed issue Open Source Friday - Squad - 2026-07-31 #235 now fails with an explicitValueErrorfor2026-07-31.