Implementing a CI process with GitHub Actions

Initially, when I was designing the guidelines for the chapters in this book, I was planning to give a sample implementation using Azure DevOps, as it has a popular CI system. However, GitHub Actions climbed up fast and quickly became the developers’ choice in configuring a CI system, so I changed my mind and I am going to use GitHub Actions instead.

GitHub Actions can deal with multiple programming stacks; one of them is .NET Core, which is what we are concerned about in this chapter.

Obviously, you will need to have a GitHub account for using GitHub Actions and you will be glad to know that the free tier gives you 2,000 minutes/month of running time, which should be enough for a small solo project.

Next, we are going to use GitHub Actions as a CI system for the project in Chapter 10, Building an App with Repositories and Document DB you don’t need to have read the chapter, we just want a solution that has a project...