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

# Quickstart

> Get QLane testing your pull requests in five minutes — sign up, connect a GitHub repo, create a project, pick a run mode, and open your first PR.

This is the shortest path to QLane testing your pull requests. By the end you'll have a structured review posted on a real PR.

## 1. Sign up

Head to [app.qlane.ai](https://app.qlane.ai) and sign in with your work email. QLane creates an organization for you on first sign-in.

## 2. Connect your repository

QLane installs as a GitHub App on the org or account that owns the repo you want to test.

1. From the dashboard, click **Connect GitHub**.
2. Pick the repositories you want QLane to test. You can change this later.

## 3. Create a project

A **project** is a QLane workspace bound to one repository.

1. Click **New project** and select the repo.
2. QLane scans for a `package.json` and a Compose file to suggest sensible defaults.
3. Confirm and create.

## 4. Pick how QLane runs your app

QLane needs a way to reach your app. Pick the mode that matches your codebase — you can change it later, and projects can mix modes across environments.

<CardGroup cols={2}>
  <Card title="Test a URL" icon="globe" href="/connect/test-a-url">
    Already have staging or a public preview? Point QLane at the URL — no build, no provisioning.
  </Card>

  <Card title="Single repo" icon="code" href="/connect/single-repo">
    One repo, one app. QLane clones, builds, and runs it on every PR.
  </Card>

  <Card title="Docker Compose" icon="layer-group" href="/connect/docker-compose">
    Run your whole stack — every service, with realistic data.
  </Card>

  <Card title="Existing previews" icon="bolt" href="/connect/existing-previews">
    Already deploying per PR with Vercel, Netlify, or Cloudflare? QLane tests on top.
  </Card>
</CardGroup>

## 5. Open a pull request

Open any PR in your repo (or push to an existing one). Within a couple of minutes you'll see:

* A **QLane** check appear on the PR.
* A new run in your dashboard under the project.

When the run finishes, you get either silence (nothing broke) or a GitHub review with per-bug comments, screenshots, and repro steps.

## Next steps

<CardGroup cols={2}>
  <Card title="Write test cases" icon="list-checks" href="/results/test-cases">
    Pin down the behaviour you care about most.
  </Card>

  <Card title="Run QLane from anywhere" icon="terminal" href="/triggers">
    Slack, Linear, Jira, Claude Code, the dashboard, the CLI.
  </Card>

  <Card title="Read a bug report" icon="bug" href="/results/bug-reports">
    See what a finding actually looks like.
  </Card>

  <Card title="Coverage map" icon="map" href="/results/coverage">
    Find the gaps before they ship.
  </Card>
</CardGroup>