CI tune-up
A tune-up reads one repository's GitHub Actions workflows and build setup and changes them to run faster on Groundbox runners. You get one pull request, with each change explained. It is free on the paid plan.
What it changes
- The runner size of each job, from the labels your plan has.
- Caching: the
cacheoption of thesetup-*actions,actions/cachekeys from lock files, Docker layers withtype=gha, ccache or sccache, Gradle and Maven. - Parallel jobs, matrix splits and test sharding.
- Steps that run twice or do nothing.
concurrencywithcancel-in-progressfor pull requests, path filters, and shallow checkouts.
It keeps what your workflows test and build the same. It never removes a test or a required check.
Start one
- Dashboard: Repos and runners, then Tune up on the repository's row.
- CLI:
groundbox tuneup owner/namestarts it and waits for the result. - MCP: the
start_tuneupandget_tuneuptools. - API:
POST /tuneupswith a key that hasci:write, thenGET /tuneups/{id}.
curl https://api.groundbox.dev/v1/tuneups \
-H "Authorization: Bearer $GROUNDBOX_API_KEY" \
-H "Content-Type: application/json" \
-d '{"repo": "you/app"}'
curl https://api.groundbox.dev/v1/tuneups/tun_... \
-H "Authorization: Bearer $GROUNDBOX_API_KEY"A tune-up takes a few minutes. A team runs 1 at a time and up to 3 a day.
Review and open the pull request
The tune-up page in the dashboard shows each change, what it should save, and the diff. Open pull request opens one pull request as you on GitHub, from the commit the tune-up read. You review and merge it like any other.
What it never does
- It runs in a Groundbox sandbox that is deleted when it ends. Nothing runs on another service's machines.
- It clones with a read-only token for that one repository. The token is not stored.
- It never reads
.envfiles, keys or credential files, and values that look like secrets are hidden before anything is read. - It never pushes to your repository. Only you open the pull request.
Before and after
Once the pull request's CI has run on Groundbox, the tune-up page shows each job's time on the pull request next to its median on the base branch before the tune-up.