Github Actions Continuous Integration for a django and Postgresql Web App
tl;dr – Here’s a working example of a Django project. We use GitHub extensively – for client projects, for internal projects & for open source. It was a matter of time for GitHub to roll their own CI & catch up with Bitbucket Pipelines & GitLab CI. Having a CI is integral part of our software development process – build & lint on every commit, deploy to staging & production from specific branches. We use either CircleCI or CodeShip, depending on the project & the needs. With GitHub Actions now being generally available for everyone, I was itching to give it a go. The final aim of this article is to provide you with a working Django + Postgres example, share my struggles during the setup. I’ll go step by step and include some of the errors that you might encounter, while trying to set things up. Terminology As with every other CI, I made the mistake to jump right in, start pasting yml configuration around & hoping for the best. Only after reading some m