Disable scheduled CI, and update Node versions #73
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
joliss
force-pushed
the
ci
branch
3 times, most recently
from
8ea430b to
2048b84
Compare
After 60 days, GitHub seems to disable the workflow. https://github.com/joliss/node-walk-sync/actions/workflows/ci.yml says "This scheduled workflow is disabled because there hasn't been activity in this repository for at least 60 days", and there are no runs listed at all, so perhaps GitHub is turning off not just the scheduled runs, but the whole workflow. Let's see if turning off the scheduling brings it back. This also replaces volta with actions/setup-node, as volta was failing on macOS.
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.
After 60 days, GitHub seems to disable the workflow. https://github.com/joliss/node-walk-sync/actions/workflows/ci.yml says "This scheduled workflow is disabled because there hasn't been activity in this repository for at least 60 days", and there are no runs listed at all, so perhaps GitHub is turning off not just the scheduled part, but the whole workflow. Let's see if turning off the scheduling brings it back.