Migrating Your GitHub CI to Hugging Face Jobs
Hugging Face published a step-by-step guide for running GitHub software test jobs on its serverless Hugging Face Jobs service instead of GitHub's own machines. Teams keep GitHub Actions in charge of the workflow, but the actual test work runs on Hugging Face hardware, including graphics processors that open-source projects rarely get for free. In a live test on the Trackio project, the switch cut standard test time by about 30 percent and added a GPU test that finished in 45 seconds for less than a cent.
Key Takeaways
- We're on a journey to advance and democratize artificial intelligence through open source and open science.
Back to Articles Migrating Your GitHub CI to Hugging Face Jobs Published June 9, 2026 Update on GitHub Upvote 8 +2 Abubakar Abid abidlabs Follow If you have a GitHub repository and you have GitHub Actions enabled, you probably use GitHub-hosted runners for CI.
- We wanted both reliable CPU CI for basic unit tests and frontend checks, but also GPU CI for tests that need to run on actual CUDA hardware.
So built an alternative: keep GitHub Actions in charge of CI, but run the jobs on Hugging Face Jobs .
- CI jobs are already command-driven, already run in clean environments, and often benefit from choosing exactly the right hardware.
For ML libraries, the GPU case is especially compelling: you can run a test suite on real GPU hardware without maintaining your own always-on runner.
- The HF Job boots an ephemeral GitHub Actions runner and registers it with the repo using that one-shot token.
GitHub assigns the pending workflow job to that runner; the runner executes the CI job, reports status back to GitHub, and exits.
- This Space should be under your own namespace or under a Hugging Face org that you have write access to.
Stats & Key Facts
- #The result: Trackio's CI now runs on Hugging Face Jobs and streams back real-time logs, cutting our CI time for CPU jobs by about 30% and enabling a whole new test suite that runs on GPU machines !
We're on a journey to advance and democratize artificial intelligence through open source and open science. Back to Articles Migrating Your GitHub CI to Hugging Face Jobs Published June 9, 2026 Update on GitHub Upvote 8 +2 Abubakar Abid abidlabs Follow If you have a GitHub repository and you have GitHub Actions enabled, you probably use GitHub-hosted runners for CI. That is the default for many projects because it is simple: add a workflow, write runs-on: ubuntu-latest , and GitHub gives you a machine.
That default is convenient, but it also has limits. GitHub Actions can be slow or down for maintenance, the hosted machines are generic, and GPU access is not something most open-source projects can just turn on. For Trackio , those limits started to matter.
We wanted both reliable CPU CI for basic unit tests and frontend checks, but also GPU CI for tests that need to run on actual CUDA hardware. So built an alternative: keep GitHub Actions in charge of CI, but run the jobs on Hugging Face Jobs . The result: Trackio's CI now runs on Hugging Face Jobs and streams back real-time logs, cutting our CI time for CPU jobs by about 30% and enabling a whole new test suite that runs on GPU machines !
For more details please read the original article at Hugging Face.
Continue Learning
Comments
Comments appear only after moderation. Your email identifies your submission to the moderator and is never displayed here.
No approved comments yet.