Skip to content

quickstart.mdx

Latest commit

 

History

History
95 lines (69 loc) · 3.57 KB

quickstart.mdx

File metadata and controls

95 lines (69 loc) · 3.57 KB
Raw
title Platform quickstart
description Connect a repository and receive your first Autter pull request review.

Use this guide to connect the Autter platform and verify that reviews appear in your source control provider.

Before you begin

You need:

  • an Autter account
  • access to a GitHub repository or GitLab project
  • permission to install or authorize the relevant integration
  • a pull request or merge request you can open for verification
Plans and included review volumes can change. See [current pricing](https://www.autter.dev/pricing) before you roll Autter out across an organization.

Connect your first repository

Open the [Autter platform](https://app.autter.dev) and sign in. Choose your source control provider and complete its authorization flow. 
<Tabs>
  <Tab title="GitHub">
    Install the Autter GitHub App on the account or organization that owns the repository.
  </Tab>
  <Tab title="GitLab">
    Authorize the Autter GitLab integration for the account, group, or project you want to use.
  </Tab>
</Tabs>
Select the repository or project Autter should review. Start with one active repository while you evaluate the feedback. Open a pull request or merge request in the connected repository. Autter starts the review from the proposed diff and available repository context. Look for an Autter review summary, inline findings, or an Autter check in the pull request interface.

Placeholder showing a customer connecting a GitHub or GitLab repository to Autter

{/* TODO: Add approved screenshots for the current GitHub and GitLab authorization screens. */}

Evaluate the first review

Check that the review gives the author enough context to act:

  • the affected code or behavior
  • why the finding matters
  • a proposed fix when Autter can provide one
  • the severity or merge impact

If the feedback is too broad or too noisy, adjust the review behavior and add team rules. See Configuration.

Add a team rule

Autter supports team standards written in natural language. Define a small, testable rule such as:

Payment handlers must verify the authenticated account owns the payment method before creating a charge.

Apply the rule to the relevant repositories, then test it with a pull request that contains a representative change. See Custom rules for a safe rollout process.

Add AI authorship context

Install the Autter CLI when you also want line-level attribution for code written by coding agents.

curl -sSL https://autter.dev/install.sh | bash
autter status

The CLI can remain local-only or connect to your Autter organization. See Install the CLI and Data and privacy.

Troubleshoot the connection

If no review appears:

  1. Confirm the repository is included in the integration's access scope.
  2. Confirm the pull request targets the repository's normal review branch.
  3. Check the Autter platform for a connection or review status.
  4. Reopen or update the pull request after fixing access.

{/* TODO: Add the approved platform support path for failed hosted reviews. */}