GitHub Actions: Optimization and Performance
Slow CI is a productivity killer. Here's how to slash your GitHub Actions workflow times—with real examples, benchmarks, and the caching strategies that actually work.
Slow CI is a productivity killer. Here's how to slash your GitHub Actions workflow times—with real examples, benchmarks, and the caching strategies that actually work.
Push and pull_request are just the beginning. Here's how to trigger workflows from Slack, schedule nightly builds, chain workflows together, and turn GitHub into a surprisingly capable automation platform.
Your GitHub Actions workflows have access to your secrets, your code, and your deployment pipelines. Here's how to lock them down before someone else does.
Your GitHub Actions workflows don't have to be unmaintainable YAML spaghetti. Here are the design patterns, refactoring techniques, and organizational strategies that keep workflows clean as they grow.
GitHub Actions can do far more than run your tests. Here's a tour of the surprising, useful, and unconventional things people build with workflows—and the start of a series going deeper.
I built a CLI that converts documentation docsets to Markdown files—because Apple's online docs don't work without JavaScript, and I don't want MCPs in my workflow.
I've been building command-line tools for my own workflows, and I've learned a few things about what makes a CLI actually pleasant to use. Here's what I wish someone had told me earlier.
Everyone's rushing to build MCP servers for their AI coding workflows. I tried a few, ripped them all out, and went back to plain CLIs. Here's why.
I built a minimal, scriptable task tracker that stores issues as plain Markdown files—perfect for agentic workflows where AI assistants need to track and manage work.