keep-workflows-enabled: Disable all workflows before enabling #151
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
Some new scheduled workflows have been added since this list was last
updated.
The list was generated programmatically using:
gh api "search/code?q=org:nextstrain+path:.github/workflows+schedule&per_page=100" | \
jq -r '.items[] | " - { repo: \(.repository.name),\(" " * (16 - (.repository.name | length)))workflow: \(.name) }"' | \
LC_ALL=C sort -f
The last user that enabled a disabled workflow or updated the schedule is the one that "owns" all the future scheduled runs of that workflow and receives any email notifications if configured in the user's settings.¹ This makes nextstrain-bot the owner of all the workflows listed here, not just the ones that were automatically disabled due to inactivity. ¹ https://docs.github.com/en/actions/concepts/workflows-and-actions/notifications-for-workflow-runs
joverlee521
approved these changes
Dec 8, 2025
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.
Description of proposed changes
The last user that enabled a disabled workflow or updated the schedule is the one that "owns" all the future scheduled runs of that workflow and receives any email notifications if configured in the user's settings.¹
This makes nextstrain-bot the owner of all the workflows listed here, not just the ones that were automatically disabled due to inactivity.
¹ https://docs.github.com/en/actions/concepts/workflows-and-actions/notifications-for-workflow-runs
Related issue(s)
https://github.com/nextstrain/private/issues/194
Checklist