inlinedocs
Portal ↗

Get started

Quickstart

This walks you from zero to inline reviewing your pull requests. You’ll sign in, connect GitHub, enable a repository, and open a PR.

# 1. Sign in

Open the portal and sign in with your Microsoft work account (Entra ID). The first person from your organization to sign in gets a personal workspace; teams are organized into organizations you can switch between from the top of the sidebar.

# 2. Connect GitHub

inline connects to GitHub in one of two ways — see Connecting GitHub for the full comparison:

  • GitHub App (recommended) — installs the inline bot into your org. Reviews post under the bot’s identity and GitHub delivers events automatically.
  • OAuth (Nango) — connects under your own GitHub account from the portal. inline provisions repo webhooks for you.

Go to Repositories and follow the connect flow for whichever mode your org uses.

# 3. Enable a repository

Connecting makes repos visible; enabling turns on reviews. On the Repositories page, toggle a repo enabled. That’s the only required step — everything below is optional tuning.

# 4. Open a pull request

Open or update a PR in the enabled repo. Within a minute or two:

  1. inline picks up the change.
  2. A fast model triages it; if it’s substantive, the deep model reviews it.
  3. inline posts a summary comment plus any inline findings, and — if you enabled it — a walkthrough link.

If inline has nothing worth saying, it says nothing. Zero comments is a successful review.

# 5. Interact on the PR

You can talk to inline right in the PR by commenting:

text
@inline full review        # re-review the whole PR from scratch
@inline ask <question>     # ask about the change
@inline learn <rule>       # teach it a convention to remember

See Conversations for the full command set.

# 6. Tune it

Once you’ve seen a few reviews, tune to taste in the portal:

  • Severity threshold and custom instructions — review config.
  • Merge gate — make inline / review a required check (merge gate).
  • Learnings & skills — teach conventions and attach expertise (learnings).
  • Auto-fix, sandbox tests, walkthroughs — opt-in automation.

# Next steps