Pipelines
Connect your CI provider from inside Studio — view runs and logs, trigger or cancel a run, and publish a starter workflow file.
The Pipelines tab connects Studio to your CI provider (GitHub Actions and others):
| Run | Status | Branch | Commit | When | Duration | |
|---|---|---|---|---|---|---|
| #214 | running | main | a91cd02 | just now | — | |
| #213 | failed | fix/checkout-toast | e2f7a13 | 18m ago | 54s | |
| #212 | success | main | 9b0d441 | 1h ago | 48s | |
| #211 | success | main | 77aa9f0 | 3h ago | 51s |
- Connect — enter a token in the native connect dialog; it's stored locally alongside the same credentials the CLI reads.
- Runs & logs — a live table of runs for the detected repo/branch, with logs on demand.
- Trigger & cancel — kick off or stop a run without leaving Studio.
- Publish a starter workflow — generate and publish a starting
testrelic.ymlCI workflow for the repo.
No repo yet? Publish to GitHub
If the project has no remote at all, the empty state adds a second path once GitHub is
connected: Publish to GitHub (private). One click creates a new private repo under your
account, wires it as origin, and pushes — then seeds the chat to generate the workflow, set
the TestRelic secrets, and trigger the first run. It's the zero-repo route into CI, separate
from the header Git button's own publish/sync flows. See
Git integration for both.
Connect a provider above (your token stays on this machine), then "Set up in chat" — the agent generates the workflow, sets the TestRelic secrets locally, and triggers run #1. Runs stream into this table.
This project isn't on GitHub yet — CI needs somewhere to run.
Next steps
→ Git integration · Workspace · Overview
Workspace
The Code and Cloud views, the Tests list, test detail, chat (agent runs, cards, the changes chip and the Local mode Skill), Settings, Automations, Run targets, issue detection, fix & re-run and the terminal inside TestRelic Studio.
Git integration
Studio's header Git button turns version control into buttons instead of a terminal — track, publish, sync, sign in — plus the zero-repo path that gets untracked tests onto GitHub and into CI.