Skip to main content
Connect Autosana to your repositories. When you open a PR, Autosana analyzes the diff, selects and runs relevant flows, and posts results with videos as a PR comment.

​
How it works

  1. You open a PR
  2. Autosana analyzes the diff and selects relevant flows (editing or creating as needed)
  3. Flows run in parallel as your build completes
  4. Results are posted as a PR comment with videos and a GitHub Check

​
Setup

  1. Go to Settings > Integrations > GitHub and click Install GitHub App
  2. Select your GitHub account/organization and choose repositories
  3. Toggle E2E Autopilot per repo to automatically analyze and test PRs
Each repo also has a Code Review toggle for automatic AI code review on PRs — see Code Review. The two toggles are independent; enable both to get a review and test results on the same PR.

​
If you aren’t an owner of your GitHub organization

Click Install GitHub App anyway. GitHub sends your request to an owner of the organization. When the owner approves it, GitHub brings them to Autosana. They sign in with GitHub, see which workspace asked and who asked, and click Confirm. They don’t need an Autosana account. Your repositories then appear in Settings. If an owner installed the app straight from GitHub, Autosana gives them a link to send you. Open it, and Settings > Integrations > GitHub shows Finish connecting GitHub. Click Link. If you aren’t an owner, Autosana asks one to confirm: click Copy owner link and send it to them. Each new copy turns off the previous link. Settings shows where a connection stands and what to do next:
You need to be an admin of your Autosana organization to install the GitHub App, link it, retry, copy an owner link, or cancel a request.
Set up the GitHub Action for App Uploads so Autosana can access builds for each PR.

​
Several workspaces in one company

Workspaces in the same company can share one GitHub App installation. In each workspace, go to Settings > Integrations > GitHub and click Install GitHub App, then pick the same GitHub organization. Each repository belongs to one workspace at a time.
  • In other workspaces lists repositories that another workspace in your company holds. It shows even before this workspace connects GitHub. Click Move here to bring one into this workspace. If this workspace isn’t connected yet, the move connects it to that repository’s GitHub organization. The repository’s synced tests leave the other workspace and re-sync here. Its run history stays in the other workspace. Build uploads from the other workspace then stop posting checks for that repository. A workspace connected to a different GitHub organization must disconnect before it can move the repository.
  • Disconnect from this workspace stops this workspace using the installation. It is refused while code-managed tests or PR review are on for any of this workspace’s repositories, or while tests, suites or hooks come from one. If another workspace in your company still uses it, this workspace’s repositories move there. The app stays installed on GitHub.
  • Uninstalling the app on GitHub removes it from every workspace.
If Settings says the organization is already connected to a workspace in another company, switch to that company’s workspace, or ask its admins to disconnect it. You need to be an admin of the workspace to move a repository or disconnect.

​
Code-Managed Flows

Instead of authoring flows in the dashboard, you can define flows, suites, and hooks as files in your repository’s .autosana/ folder. Connect the repo in Settings > Integrations > GitHub; Autosana automatically syncs .autosana/ on every push to your default branch and previews changes on pull requests. Parse errors surface as line annotations on the Autosana - Code-Managed Flows GitHub check, and the resulting flows are read-only in the dashboard. See Code-Managed Flows.

​
@autosana

Tag @autosana in a PR comment on any connected repository — no toggle needed. Ask questions, request specific tests, re-run failures, or adjust instructions. The agent responds as a PR comment.

​
Managing Repositories

Go to Settings > Integrations > GitHub and click Manage Installation. It opens the app’s settings on GitHub, where you can add or remove repositories.