Github-Actions

GitHub Actions: Unified Build Pipeline for Multi-Repo Application

Common Misconceptions about GitHub Actions

The other day, I was working with a customer who was planning a migration from JetBrains TeamCity to GitHub Actions. They expressed a concern that GitHub Actions does not work well in multi-repo setup; they were used to having build pipelines separate from the source code distributed across multiple repositories.

GitHub Container Registry. Keeping traffic below the spending limit.

GitHub Container Registry is a great service. It’s free for public repositories and it’s integrated with GitHub Actions. Unfortunately, it’s not free for private packages. The free tier allows 1 GB of data transfer per month. What happens when you reach the limit depends on your payment profile. You will either be prevented from downloading your images or you’ll be charged for the consumed traffic.

Integration tests for .NET CLI tools

I’ve spent Saturday evening working on a small project. I’ve built a .NET clone of tree utitly. You know, the one that renders a nice tree view for a given directory.

GitHub Environment Protection with Tags

A recent request from a customer caught my attention. They were trying to set up a CD pipeline that should deploy packages to production when there is a new tag pushed to the repository. At the same time, they wanted some control over the process so that not everyone can init a release by pushing a tag to the repository.