Setting up a build process
Every time some new code is pushed to a remote repository, we must run a set of checks to ensure the quality of the code we’re providing. Here and in the following chapters, we set up checks for coding standards and tests for visual regression and JavaScript. Of course, you can (and should) test more (using tools such as Behat (https://docs.behat.org), for example).
As we’re using GitHub as our code repository, we define a GitHub action (https://github.com/features/actions) to run all our checks. GitHub Actions is free for public repositories and is limited to 2,000 minutes of execution every month for private projects.
GitHub Actions basically runs a set of commands on our code base in a Docker container, quite similar to what we’ve done until now on our local environment. To simplify the setup even further, we’re also going to use DDEV in the GitHub Actions pipeline.
