configure keep alive workflow to keep chocomilk alive #39
Conversation
This file contains 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
The keep-alive workflow explicitly needs to keep the chocomilk workflow alive, by default it only keeps itself active.
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 keep-alive workflow explicitly needs to keep the chocomilk workflow alive, by default it only keeps itself active.
This was dfferent with "v1" which triggered dummy commits. "v2" of the keep-alive workflow uses the GitHub Actions API to keep the commit history clean, but if kept in a separate workflow file (which seems reasonable), it needs to iterate all workflows individually (in this case, chocomilk).