Update CI and release strategy #315
Merged
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
This simplifies the CI a bit and also moves to a process that I'm a bit more familiar with. Mainly, everything for releases should now be able to be handled fully by just creating a tag. I've found this to be much easier to manage. I also removed the `state.yml` since it's currently not working, and I'm not sure how I feel about having something that will auto-close issues.
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.
This simplifies the CI a bit and also moves to a process that I'm a bit
more familiar with. Mainly, everything for releases should now be able
to be handled fully by just creating a tag. I've found this to be much
easier to manage.
I also removed the
state.ymlsince it's currently not working, and I'mnot sure how I feel about having something that will auto-close issues.