Add support for "every n days" long-form schedule syntax#7352
Merged
Conversation
- Modified parseInterval() in schedule_parser.go to accept "days" as a valid unit - Added support for "every 1 day" (singular) -> "0 0 * * *" (daily) - Added support for "every n days" (plural, n>1) -> "0 0 */n * *" (every n days) - Updated test cases to expect "days" to work instead of erroring - Added test cases for "every 2 days", "every 3 days", "every 7 days", "every 10 days", "every 14 days", and "every 1 day" - Updated fuzz test corpus to include valid "days" examples and remove from invalid list - All tests pass successfully Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Add syntax for scheduling every n days
Add support for "every n days" long-form schedule syntax
Dec 23, 2025
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
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.
The schedule parser accepted short-form
every 2dbut rejected long-formevery 2 days, inconsistent withevery 2 hoursandevery 10 minutes.Changes
parseInterval()to accept "days" as valid unit alongside "minutes" and "hours"every 1 day→0 0 * * *,every n days→0 0 */n * *Example
Compiles to:
Both
every 2dandevery 2 daysnow produce identical output.Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
https://api.github.com/user/usr/bin/gh gh api user --jq .login it/ref/tags/v5 --version /usr/bin/infocmp(http block)/usr/bin/gh gh api user --jq .login it/ref/tags/v5 %(refname) /usr/bin/git --merged fbaa3ad27fdd4c63rev-parse modules/@npmcli/--show-toplevel git -C tags/v6 rev-parse /opt/hostedtoolcache/go/1.25.0/x64/pkg/tool/linux_amd64/vet 3-23b8fd6302d7/hinfocmp(http block)/usr/bin/gh gh api user --jq .login ithub/workflows --json /usr/bin/git --jq .owner.login + "-1 64/pkg/tool/linuxterm-color git conf�� 3014-16824/test-3205709398/.github/workflows(http block)If you need me to access, download, or install something from one of these locations, you can either:
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.