CI on TanStack Source
You want each push and each pull request tested, and no merge until the tests pass.
A workflow is a TypeScript file in .source/workflows/. The forge runs each of its jobs in a container of its own. Each run gets a trust level, and the level decides which secret values and permissions the jobs get. You can run the same job on your machine with src ci run.
Start here
- Your first workflow: write a workflow, push it, and see a green check on a pull request.
- Run CI jobs on your machine: run a job as the forge runs it, and fix it without a push.
- Trust levels and secrets: give each trust level its own secret values and permissions.
- Branch rules: block a merge until the required checks pass.
By task
- Your jobs spend minutes on setup and installs: Start jobs warm with the install of an earlier job.
- You keep the CI of many repositories: Share steps across repositories with
src:imports and one pinned version. - You move from GitHub Actions: Move from GitHub Actions converts your YAML workflows.
- A run failed, and you want an agent to fix it: turn on CI self-heal in the software factory. It reproduces the failure, fixes the cause and pushes the fix.
- You opened a pull request from a fork: Pull requests from a fork says why your run waits, and what it can do.
- You look up an option, a limit or a command: the CI reference. The npm package
@tanstack-source/cihas a short README.