Skip to content
MergeRay/ docs

Search documentation

Local documentation search Tab to navigate · Esc to close

How review works

Follow a source change through its surrounding constraints to the evidence behind a finding.

On this page From a changed rule to a findingRead the evidence in contextCoverage and the merge decision

From a changed rule to a finding

A small diff can change how an element fits its parent. This walkthrough illustrates a fixed-width checkout summary and the source relationships that explain its overflow. It does not run an analysis of your repository.

INSIDE THE REVIEW
ILLUSTRATIVE WALKTHROUGH

Read the changed source

checkout.css · base → head
DIFFCONTEXTEVIDENCE
01 / Change

It starts with one line.

A flexible checkout summary becomes a fixed-width element. The diff is small. Its layout impact depends on the space around it.

checkout.css
.summary {
  width: 420px;
}
CSSHighlighted: 29 · Read-only
BASE 100%HEAD 420px

Read the evidence in context

The example assumes a non-shrinking, border-box element with a 420px width. Its parent has 328px available in a modeled 360px viewport, leaving 92px beyond the parent boundary.

  1. Change: compare the authored width at the exact Base and Head revisions.
  2. Trace: connect the changed rule to its component and the available parent width.
  3. Evidence: review the finding, source location and assumptions together.
Explore the illustrative workflow

Coverage and the merge decision

A supported finding does not establish that every layout has been checked. Dynamic content and unsupported semantics may remain inconclusive; always read coverage alongside the finding.

The open clients send bounded committed source to the private hosted engine. The walkthrough is an illustration of the review concept, not a local engine or a guarantee of a particular analysis time. You decide how to correct the code and whether to merge.

Understand result coverage