# SuperCI Blog

- [GitHub Actions limits: time, memory, disk, cache and more](https://superci.dev/blog/github-actions-limits.md): Every GitHub Actions limit in one place: job time, memory, disk, jobs at once, the matrix, cache, storage, the API and spending, and which can be raised.
- [GitHub Actions budget is preventing further use: what to do](https://superci.dev/blog/github-actions-budget-preventing-further-use.md): Why GitHub says "The job was not started because an Actions budget is preventing further use", which budget it is, and how to get jobs running again.
- [GitHub Actions out of memory: exit code 137 and heap errors](https://superci.dev/blog/github-actions-out-of-memory.md): Why GitHub Actions jobs run out of memory: how much RAM each runner has, what exit code 137 means, and how to fix heap errors in Node, Java and test runners.
- [No space left on device in GitHub Actions: causes and fixes](https://superci.dev/blog/github-actions-no-space-left-on-device.md): Why GitHub Actions jobs run out of disk: how much space each runner really has, what fills it (Docker most of all), and five ways to get room back.
- [GitHub Actions time limit: how to run jobs past 6 hours](https://superci.dev/blog/github-actions-6-hour-limit.md): GitHub Actions' time limits: a job stops at 6 hours on GitHub's runners and timeout-minutes defaults to 360. Three ways to run longer jobs.
- [Waiting for a runner to pick up this job: what to check](https://superci.dev/blog/waiting-for-a-runner-to-pick-up-this-job.md): Why a GitHub Actions job stays at "Waiting for a runner to pick up this job": labels, plan limits, larger runners, billing, your own runners and autoscalers.
- [Self-hosted GitHub Actions runners on AWS](https://superci.dev/blog/github-actions-runners-on-aws.md): Five ways to run GitHub Actions jobs in your own AWS account: a runner on EC2, ECS on Fargate, CodeBuild, ARC on EKS, or a fresh machine for each job.
- [What a GitHub Actions minute costs in 2026](https://superci.dev/blog/github-actions-pricing.md): GitHub Actions prices by runner size after the January 2026 cut, how minutes are counted, what happened to the self-hosted charge, and ways to pay less.
- [Self-hosted GitHub Actions runners without Kubernetes](https://superci.dev/blog/self-hosted-runners-without-kubernetes.md): GitHub's own way to scale self-hosted runners needs a Kubernetes cluster. What one fresh machine per job takes without one, and four ways to get it.
- [GitLab CI jobs on AWS spot machines](https://superci.dev/blog/gitlab-ci-aws-spot-machines.md): What a GitLab CI minute costs on GitLab.com and on an AWS spot machine, how GitLab's own autoscaler does it, and a way with no runner manager to keep.
- [GitHub Actions jobs in Cloudflare containers](https://superci.dev/blog/github-actions-cloudflare-containers.md): What a GitHub Actions job costs in a Cloudflare container, which jobs fit in 4 CPUs and 12 GiB and which do not, and how to send jobs there.
- [GitHub Actions on spot instances: an eighth of the price](https://superci.dev/blog/cheaper-github-actions-runners-aws-spot.md): What a GitHub Actions minute costs on GitHub's runners and on AWS spot instances, where the saving comes from, what you give up, and how to set it up.
