Repository navigation
Re-own the scheduled workflows (cron lines last changed by a removed account) - #1119
Merged
Merged
Conversation
GitHub runs a scheduled workflow as the user who last changed its cron line. Those lines were last changed by an account that no longer exists, so no schedule has fired in this repository since it disappeared (zero runs with event=schedule). Disabling and re-enabling the workflows did not help. This only swaps the quote style on each cron line, so the schedules are unchanged but now belong to an active account.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Re-own the scheduled workflows after the old GitHub account went away
GitHub runs a scheduled workflow as the user who last changed its cron line.
Those lines were last changed by an account that no longer exists, so no
schedule has fired in this repository since it disappeared (zero runs with
event=schedule). Disabling and re-enabling the workflows did not help.
This only swaps the quote style on each cron line, so the schedules are
unchanged but now belong to an active account.
Verify after merge:
gh api 'repos/{owner}/{repo}/actions/runs?event=schedule&per_page=3'should show runs within the next scheduled slot.