testdriverci-cdlisted

<!-- Generated from ci-cd.mdx. DO NOT EDIT. --> TestDriver integrates seamlessly with popular CI providers, enabling automated end-to-end testing on every push and pull request. ## Authentication On **GitHub Actions, prefer OIDC** via the published `testdriverai/action` — there's no `TD_API_KEY` secret to store, copy, or rotate. The action proves the workflow is running inside your org and TestDriver exchanges that proof for your team's key at run time. See the GitHub Actions tab below. For other CI providers (or self-hosted runners without OIDC), fall back to a stored API key from [console.testdriver.ai/settings](https://console.testdriver.ai/settings), added as a `TD_API_KEY` secret in your CI provider's settings. <Note> Never commit your API key directly in code. Always use OIDC or your CI provider's secrets management. </Note> ## CI Provider Examples <Tabs> <Tab title="GitHub Actions"> ### Authenticate with OIDC via `testdriverai/action` (recommended) Use the published [`testdriverai/action`](https://github.com/testdriverai/action) — it mints the OIDC token, exchanges it for your team's API key, and exports `TD_API_KEY` for the steps that follow. **No `TD_API_KEY` secret to store or rotate.** <Note> One-time setup: authorize the [TestDriver GitHub App](https://console.testdriver.ai) for your org so the org → team binding exists. If your org authorized the App before OIDC support shipped, re-authorize once. If the App isn't authorized, the ac