If you happen to use Github a lot, you will notice that the Actions tab is one click away. Yet Github Actions has some pros that made it a better fit for most of my use cases. In the past, I used other services such as Travis CI, Circle CI, and GitLab CI. Github Actions is not the only service to set up a CI system. This is how a Continuous Integration process generally looks like. This will exclude variability introduced by the local developer machine. Moreover, builds and tests are running in an isolated environment. It’s useless to write tests if you are not running themĪ CI system allows you to run your tests every time you integrate a change in your codebase. You can find plenty of material online on how to write good tests, but:

Having a good CI is crucial in your development flow. With Github Actions, you can automate tasks of your development lifecycle such as build, test, analyze, bundle, release, and deploy. Github Actions is a service offered by Github to set up a Continuous Integration (CI) system for your projects hosted on Github. This first blog-post will serve as an introduction and will help you to get started with Github Actions. While I migrated real-world projects I collected tips and tricks that will help you get your CI up to speed. In this blog-post series, I will walk you through how to set up your CI with Github Actions. I have to admit that I was amazed by how easy it was to set up, together with the performance boost I gained from it. I’ve recently spent some time migrating several projects of mine to Github Actions. One of the first things I set up when working on a project, is a Continuous Integration (CI) system.

How-to Github Actions: Building your Android App

Github android studio project