GitHub has been evolving rapidly in the last few years. With the introduction of GitHub Actions and GitHub Packages, your continuous integration (CI) pipelines can be entirely implemented without leaving GitHub, reducing context switching and increasing productivity for engineers. In this post, we will work through setting up pipelines for a Docker based project including pull request (PR) validation, CI, publishing of CI images and publishing of release images, all in GitHub.

In Part 2 of this series, we added the necessary code to package the console app as a .NET Tool that can be published to NuGet. In this post, we’re going all in on the DevOps, including pull request validation, publishing a CI package and publishing a Release package. Note: I’ve gone ahead and added some tests so our CI/CD has something to test, so the main program looks slightly different compared to the first two posts, but hopefully not too much!