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

# Quickstart: Connect your repo and test your first PR

> Sign in with GitHub, install the Opslane app, select a repository, and get pass/fail results with screenshots and video on your next pull request.

Getting Opslane running takes about two minutes. You sign in with GitHub, install the Opslane GitHub App on one or more repositories, and then open a pull request — Opslane handles everything else. The next time a PR is opened, you will see a comment appear with the test results, screenshots, and a video of the browser session.

<Steps>
  <Step title="Sign in with GitHub">
    Go to [app.opslane.com/auth/github/login](https://app.opslane.com/auth/github/login) and click **Sign in with GitHub**. Opslane uses your GitHub identity for authentication. No separate account or password is required.
  </Step>

  <Step title="Install the Opslane GitHub App">
    After signing in, you are prompted to install the Opslane GitHub App. Click **Install GitHub App** and choose whether to install it on all repositories or only specific ones.

    <Info>
      You need admin access to the repositories you want to connect. If you are part of a GitHub organization, you may need an organization owner to approve the installation.
    </Info>
  </Step>

  <Step title="Select the repositories to test">
    Back in the Opslane dashboard, select which repositories Opslane should watch. You can add more repositories at any time from the **Repositories** settings page.
  </Step>

  <Step title="Open a pull request">
    Push a branch to one of your connected repositories and open a pull request as you normally would. Opslane detects the PR event automatically — no webhook configuration needed.

    <Tip>
      On your first run, Opslane crawls your app to establish a baseline. This run focuses on mapping your app's flows rather than checking for regressions, so it may not flag any issues. Subsequent runs compare against this baseline and will catch changes.
    </Tip>
  </Step>

  <Step title="Review the results on your PR">
    Within a few minutes, Opslane posts a comment on your pull request. The comment includes:

    * A **pass/fail status** for each flow tested
    * **Screenshots** captured at key points during the session
    * A **video recording** of the full browser run

    If Opslane detects a regression, it sets the GitHub check to failing. This blocks the merge until the issue is resolved or a team member manually overrides the check.
  </Step>
</Steps>

## What to expect on your first run

The first time Opslane runs on a repository, it does not have a baseline to compare against — so it focuses on crawling your app and learning what flows exist. You will still get a comment on the PR with screenshots and a video, but regression detection kicks in from the second run onward.

<Note>
  Opslane is free during the early access period. No credit card is required to sign up.
</Note>

## Next steps

<CardGroup cols={2}>
  <Card title="How it works" icon="magnifying-glass" href="/how-it-works">
    Understand the three-phase pipeline: Connect, Verify, and Ship.
  </Card>

  <Card title="Introduction" icon="book-open" href="/introduction">
    Learn how Opslane compares to Playwright and Cypress and how it handles security.
  </Card>
</CardGroup>