GitHub Actions problems and fixes
Each page names a common GitHub Actions problem, explains the cause, and gives a fix you can use today. Then it shows how Codemany fixes it for you.
All problems
GitHub Actions slow? 7 causes and how to fix eachGitHub Actions slow? Most time goes to cold caches, small 2-core runners, queues and downloads. Find your cause, apply the fix, and measure the change.
GitHub Actions macOS jobs slow? Use your own MacGitHub Actions macOS jobs are slow and cost more per minute. See why macos-latest jobs queue and start cold, and how your own Apple silicon Mac fixes it.
GitHub Actions free limits: minutes running out?Hit your GitHub Actions free limits? See how included minutes are counted, why macOS uses them fastest, and how jobs on your own machines avoid them.
GitHub self-hosted runner offline? Find the causeGitHub self-hosted runner offline? Check the service, sleep, network and token in that order. Fix it by hand, or let Codemany restart and alert you.
GitHub Actions no space left on device: fix itGitHub Actions no space left on device? Find what fills the disk, free space safely with Docker and cache cleanup, and stop it coming back on runners.
GitHub self-hosted runner cleanup: dirty workspacesLeftover files on a GitHub self-hosted runner break the next job. See why workspaces stay dirty, cleanup steps that work, and how single-use runners help.
GitHub Actions waiting for a runner to pick up jobGitHub Actions waiting for a runner to pick up this job? Check labels, runner groups, repo access and busy machines. Fix each cause in a few minutes.
Check Xcode version in GitHub Actions and pick oneCheck Xcode version in GitHub Actions, select the one your app needs, and stop builds breaking when macos-latest changes. Pin Xcode on your own Mac too.
Codemany is $20 a month for 2 machines. Try it free for 14 days, with no card.