Update TagBot.yml #151
Merged
Update TagBot.yml #151
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
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.
GitHub has started automatically disabling Actions workflows that run on a schedule for repositories that have not seen any activity for 60 days. This happened both to our TagBot and our CompatHelper.
Following this thread on Julia discourse, "inactive" repositories will not trigger the TagBot on schedule, but whenever the TagBot commits on issue #105. However, this requires the changes in
TagBot.ymlfound in this PR are required.I do not know whether there is already a user-friendly and easy option to keep our CompatHelper alive.