Simplify setup and use GitHub Actions for CI. #11
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
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.
Hello, we have detected this gem is one of the crucials in RubyGems.org ecosystem and is currently missing active CI. I tried to simplify the CI setup as much as possible to follow current best practices and added GitHub Actions with all supported Rubies. There is ancient rubocop setup I have ignored on CI for now. Feel free to ping me if help with maintenance is needed. I'm happy to for example upgrade the rubocop setup in followup or add more Rubies to CI matrix.
CI can be seen in action at RubyElders#1.