Basic setup for github actions #32
Open
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
|
Jeeze @c42f I'm really sorry I never acted on this way back when, I must have forgotten or missed it. Do you have any ideas as to why the CI workflows aren't running? |
|
Possibly because you need to enable it in the package settings? Possibly something else? I'd totally forgotten I did this PR 😅 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I noticed there's no
gittags for 0.2.6 or 0.2.7, and that this repo still has a Travis CI setup (likely completely obsolete at this point?)So I thought it could be helpful to set up TagBot to do release tagging and we may as well have a modern github actions setup for CI as well.