> ## Documentation Index
> Fetch the complete documentation index at: https://docs.testsprite.com/llms.txt
> Use this file to discover all available pages before exploring further.

# GitHub App & GitHub Actions

> Run TestSprite on every pull request: when to use the GitHub App and when to use GitHub Actions, and how results land in the PR.

*Video by **Execute Automation** · 12:19 · English*

[https://www.youtube.com/embed/8ZuOrdcBgJ4](https://www.youtube.com/embed/8ZuOrdcBgJ4)

## What You'll See

* **Choosing an integration**: the **GitHub App** (ideal for managed platforms like Vercel or Netlify) versus **GitHub Actions** (full control over the pipeline)
* **The build phase**: building and starting the app with Docker Compose inside CI
* **Reaching the app from TestSprite**: using a Cloudflare tunnel so TestSprite's cloud can test an app running in CI
* **Reading the results**: execution videos and pass/fail reports, right in the pull request

## Try It Yourself

> **[GitHub Integration](https://docs.testsprite.com/web-portal/integrations/github-integration.md)**
>
> Connect the GitHub App and set up triggers

> **[Test Schedules](https://docs.testsprite.com/web-portal/maintenance/monitoring.md)**
>
> Run the same suite on a cadence, too

> [!NOTE]
>
> Recorded in April 2026, before TestSprite 3.0. The Web Portal screens look different today, but the integration approach still applies. See [GitHub Integration](https://docs.testsprite.com/web-portal/integrations/github-integration.md) for the current setup.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.