GitHub Actions to guard your workflow
At Evrone, we build projects in a number of programming languages, including Ruby, Go, Rust, Python, Elixir, etc., and link various linters to each project. To ensure that our code follows all quality requirements, we run linters using CI services for any commit sent to GitHub.
It is very important to us that the result of linters’ work can be seen on GitHub, for example, in the form of comments to pull requests. That’s why we use reviewdog that automates code review and provides integration of any linter with GitHub.
As cool as reviewdog is, we still had to spend time setting up CI services to run linters for each project. But that all changed when GitHub announced GitHub Actions, a new tool for automating workflows.
Having switched to GitHub Actions, we decided to write our own actions to run popular linters. It allowed us to simplify the process of connecting linters to any project. Find all the GitHub actions in the full article.