GitHub Actions articles
Short, plain guides to how GitHub Actions works. Each one explains a topic, shows real YAML, and says where your own runners help.
All articles
GitHub Actions cache: how actions/cache works and failsGitHub Actions cache saves files between jobs with actions/cache. Learn keys, limits, when caches miss, how to clear them, and how a local cache helps.
GitHub Actions timeout-minutes: stop stuck jobsGitHub Actions timeout-minutes ends a job or step that runs too long. See the default limit, where to set it, and how to find why a job hangs at all.
GitHub Actions limits: jobs, time and API rate limitsGitHub Actions limits cap job time, concurrent jobs, queue time and API calls. See each limit, what hits it first, and what changes on your own runners.
GitHub Actions Docker in Docker on a self-hosted runnerRun Docker in Docker in GitHub Actions: when you need it, the risks, and how to build images on a self-hosted runner without sharing the Docker socket.
GitHub Actions Docker cache: faster image buildsGitHub Actions Docker cache cuts image build time. Compare cache-from, the gha cache backend and a local registry mirror, with copy-paste workflow steps.
GitHub ARM runners: arm64 CI on Apple silicon and LinuxGitHub ARM runners build and test arm64 code natively. See hosted arm64 options, why emulation is slow, and how to run arm64 jobs on your own machines.
GitHub Actions matrix: run jobs in parallel the right wayGitHub Actions matrix runs one job across many versions or systems. Learn include, exclude, fail-fast and max-parallel, and how many machines you need.
Blacksmith vs GitHub Actions runners vs your own machinesBlacksmith vs GitHub Actions runners vs your own Mac or Linux box: compare where jobs run, macOS support, pricing model and setup in one honest table.
Codemany is $20 a month for 2 machines. Try it free for 14 days, with no card.