Switch from TravisCI to Github Actions #120
Closed
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
|
Thanks for the contribution @westonganger I was thinking about this switch but as far as I remember I wasn't able to do that because I didn't have proper permissions. I would like to keep all DBs, but before even start discussing that I want to understand if I am able to activate Actions for the repo |
Merged
|
I've checked everything and I can enable Github Actions, which is great
I am going to close this PR as it will be simpler to play with the setup on my own(in this PR #124) rather than requesting changes here |
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.
Switch from TravisCI to Github Actions so that we have a CI suite again
This github workflow was extracted from one of my many gems so it should be basically ready to go.
I have changed the tests to only run against sqlite as I think this gem is totally database independent. If we want to test against mysql or pg its just simple changes to the the following files:
.github/workflow/test.yml, Appraisals, Gemfile