Automating Workflows with GitHub Actions

GitHub Actions are incredibly useful for core workflows across the entire development lifecycle, including testing, code quality reviews, packaging, and deployment. They allow you to automate tasks in your GitHub repository, such as building and testing your code, deploying your application, and more. GitHub Actions are event-driven, meaning that you can trigger a workflow on specific events, such as pushing code, creating a pull request, or releasing a new version of your software.

Nov 12, 2023

Setting up Hosted macOS GitHub Actions Workflows for Electron Builds

Last week, I wrote about releasing Electron applications on macOS, going into detail on the specific steps required to go from source code to packaged application. Building your app on your development machine is one thing, but ideally, you want to publish new builds as soon as a commit is merged, irrespective of who pushed the change on your team. If you’re working in a bigger team, you also want to keep your code signing secrets, well, secret....Electron, Systems Architecture, Automation, CI/CD, GitHub Actions

Apr 24, 2022

Required GitHub Actions Jobs in a Monorepo

Two weeks ago, I wrote about enforcing required status checks in GitHub actions. This was required in scenarios with sharding or running tests in parallel....Automation, CI/CD, GitHub Actions

Apr 09, 2022

The Required GitHub Status Check That Wasn't

A very important GitHub feature for teams is to configure branch protections. These typically include requiring pull requests and a minimum number of reviews, preventing force pushes to main branches, signing commits, and most importantly, passing status checks....Automation, CI/CD, GitHub Actions

Mar 27, 2022

Building and pushing Docker images within GitHub Actions

Building and pushing Docker images is one of the most common tasks in the deployment pipeline of most engineering teams. We usually want to build the images ahead of time to create a repository of images we can use for our deployments, or are required to do so in case of serverless deployments where you just supply your image tag....Automation, CI/CD, GitHub Actions