375134ea04
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.
18 lines
539 B
Plaintext
18 lines
539 B
Plaintext
## References
|
|
|
|
> Related Issues/Pull Requests/errors/etc...
|
|
|
|
## Objectives
|
|
|
|
> What are the objectives of these changes?
|
|
|
|
## Visual Changes
|
|
|
|
> Any visual changes? please attach screenshots (or gifs) showing them.
|
|
> If modified views are public (not the admin panel), try them in mobile display (with your browser's developer console) and add screenshots.
|
|
|
|
## Notes
|
|
|
|
> Mention rake tasks or actions to be done when deploying this changes to a server (if any).
|
|
> Explain any caveats, or important things to notice like deprecations (if any).
|