Austen Stone Blog

If you've modernized a CI/CD pipeline in the last couple of years, you've heard the gospel of OpenID Connect: stop hardcoding long-lived AWS IAM keys in your repository secrets.

Your laptop is about to stop being where work happens.

When you take an agent out of your IDE and put it on a cron job or a GitHub event trigger, everything changes.

Just like you use Copilot in VS Code or the Coding Agent from an issue, you can run those same agentic workflows triggered on GitHub events, inside Actions.

Actions isn't just your CI/CD pipeline.

The ROI bar for automation just hit the floor.

Discussions around AI frequently revolve around this end goal of automation.

So it's 12:51 on a Wednesday afternoon and I've got nothing in the fridge.

I've been experimenting using AI coding agents in GitHub Actions to automate workflows, generate code, and enhance my development process.

I love taking photos, but I don't love the hassle of hosting them myself.

I'm always looking for ways to work more efficiently and deliver better code faster.

I've created a comprehensive GitHub Actions cheat sheet inspired by the Learn X in Y Minutes format.

I've migrated my portfolio from Angular to Docusaurus to focus more on content and less on maintenance.