Run the test suite using GitHub Actions
Using GitHub Actions has a few advantages over using Travis CI: * More jobs can be run in parallel * All CONSUL repositories on GitHub will be configured automatically Besides, Travis have recently changed their policy twice. First, they announced their site for free software projects would be shut down but free software projects could still use their site for private projects. And then, they limited the usage of their services for free software projects. Just like we used to do with Travis, we're enabling builds for pull requests but not for pushed branches. We're also building the master branch. Even if we never push to the master branch directly, we're aware other CONSUL repositories do, so we're running the tests for this case.
This commit is contained in:
@@ -33,7 +33,7 @@ If you want to contribute code to solve an issue:
|
||||
If you'd like us to review your pull request in good spirits, please follow our coding conventions:
|
||||
|
||||
* Include specs to test any changes you've made
|
||||
* Travis CI will check whether the rest of the application is still working properly; check its build and make sure all tests are passing
|
||||
* Our CI will check whether the rest of the application is still working properly; check its build and make sure all tests are passing
|
||||
* Your pull request will be automatically reviewed by Hound CI; fix any issues it reports
|
||||
* Follow [the seven rules of a great commit message](https://chris.beams.io/posts/git-commit/)
|
||||
|
||||
|
||||
Reference in New Issue
Block a user