In this post I wanted to document some exploration I did around using GitHub Actions to automatically generate a semantic versioning compatible tag in certain circumstances. I’m going to assume the reader has a basic knowledge of both GitHub Actions and semantic versioning.

Requirements

Here are the requirements I’m trying to meet:

• Upon commit to the trunk branch, a new tag and release is created.
• There must be an easy way to indicate whether the release is a major, minor, or patch release.

There’s a number of assumptions that I’m going to go by since situations outside of these might complicate this initial investigation.

As of late I’ve been doing a lot of work with GitHub Actions, so in an attempt to minimize the number of technologies I’m using in my side projects I’ve converted this blog to using them for its build and deploy process. Overall, the experience was painless; the only hiccups were things not directly related to GitHub Actions (like forgetting to set the default region for the AWS CLI). The steps were:

Time for a confession: I’ve drifted back into some bad habits of mine around media consumption. I’ve been browsing the web and watching YouTube videos when I should be writing, coding, or spending focused time with those I love.

This last week I spent almost 28 hours on Firefox between my phone, iPad, and laptop (the 9 or so hours on my tablet and phone are most concerning). That’s almost two-thirds of a full work week! I’ve also spent 11 hours on Slack and 1.5 hours on YouTube. Add those up and it really is a full work week’s worth of time. That’s a sobering thought to say the least.