testdriverci-cdlisted

<!-- Generated from ci-cd.mdx. DO NOT EDIT. --> TestDriver integrates with the common CI providers. It lets you do automated end-to-end tests on each push and pull request. ## Authentication On **GitHub Actions, use OIDC** through the published `testdriverai/action`. Then there is no `TD_API_KEY` secret to store, copy, or change. The action shows that the workflow runs in your org. TestDriver changes 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), use a stored API key from [console.testdriver.ai/settings](https://console.testdriver.ai/settings). Add it as a `TD_API_KEY` secret in the settings of your CI provider. <Note> Never commit your API key in the code. Always use OIDC or the secrets management of your CI provider. </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 makes the OIDC token, changes it for your team's API key, and exports `TD_API_KEY` for the steps that come after. **There is no `TD_API_KEY` secret to store or change.** <Note> Do this one time: authorize the [TestDriver GitHub App](https://console.testdriver.ai) for your org. Then the org → team binding exists. If your org authorized the App before OIDC support was available, authorize it again one time. If the App is not