inlineGuide
ReferenceOpen the portal

Reviews

Auto-fix pull requests

inline can write the fix for a finding, run your tests against it, and open a separate pull request with the result. You review that pull request like any other.

Anyone on the pull request can ask for a fix. Turning auto-fix on for a repository is an admin task.

#How a fix happens

  1. inline offers a fix on the pull request.

    Where a repository has auto-fix on and a review posted findings, inline adds a checkbox to its own comment. Tick it to start.

  2. It writes the patch in a sandbox.

    The same isolated environment sandbox tests run in, cloned fresh for this pull request.

  3. It runs your tests against the patch.

    inline checks its own change before offering it to you.

  4. It opens a separate pull request.

    The fix arrives as its own pull request into your branch, so you review it and decide whether it lands.

Commenting @inline fix starts the same thing without waiting for the checkbox.

#Watching it work

/reviewsOpen in app

inline#482

WalkthroughTestsView PR

Cache review results per head SHA · by rojitha · typescript · 2 Sep

Cost

$•.••

Input tokens

184,220

Cached reads

151,008

Output tokens

6,412

Duration

1m 52s

Summary

Caches the review payload against the head SHA. The invalidation path misses force-pushes that keep the same tree.

High src/lib/review/cache.ts:88

A force-push that rewrites history without changing the tree reuses the cached review, so the new commit is never read.

bug · confidence 0.82
Medium src/lib/review/cache.ts:31

The cache key omits the severity threshold, so lowering it does not produce a fresh review.

bug · confidence 0.74

Suppressed by validation gate (2)

The findings on a review, with the state of each fix beside it.

The review page shows where each finding has got to. Queued means it is waiting, Ready means the patch is written, and In fix PR means it is in the pull request inline opened.

A patch marked In fix PR · unverified is one inline wrote but could not run your tests against. Read that one closely before merging it.

#What inline will and will not fix

inline fixes findings from its own review, and it works best on the ones with a clear correct answer: a missing null check, an off-by-one, an unhandled error path.

A finding marked Excluded is one inline left for you, usually because the change would be large enough that you should decide the shape of it. The finding stays on the pull request for you to handle.

#Turn it on

Switch Auto-fix on for a repository in Repository settings. Auto-fix is included with Pro; see Plans and billing.