Skip to content
MergeRay

Responsive layout review. From source.

Small diff.Bigger impact.

Catch responsive layout breaks before you merge. Trace supported React, Next.js and CSS findings to the source, with evidence in a GitHub Check.

Public repos free · private repos paid
01 No preview deployment02 No browser setup03 Results in your pull request

FROM DIFF TO REVIEW

How it works.

From a source change to a finding you can review in GitHub. See what broke, where it started and how much of the layout was covered.

THE REVIEW CIRCUIT

One change. Follow the evidence.

Illustrative example · acme/storefront #248

  1. Your pull request

    You change one line.

    The pull request pins two exact revisions, Base and Head. The review is bound to that comparison.

    Exact revisions
    BASE9f2b6a1HEADc4d8e70
    checkout.module.css
    width: 420px;− max-width: 100%;+ max-width: none;
  2. MergeRay

    MergeRay reads the source.

    The Action sends the selected source. MergeRay models how the layout fits together and compares Base with Head.

    Modeled comparison
    Parent space 328px
    BASE · max-width: 100%328px
    HEAD · max-width: none420px

    +92pxbeyond the parent in Head

  3. GitHub

    The result lands on your PR.

    A GitHub Check and job summary carry the finding, how certain it is, and how much was covered.

    GitHub Check
    MergeRaylimited / fail
    BASE9f2b6a1HEADc4d8e70

    Source layout finding

    warning · introduced · blocking
    Coverage
    partial
    Findings complete
    false

    Revisions checked before delivery.

Modeled example. No live repository analysis; partial coverage stays visible.

Inspect the example diff and correction

Illustrative source example: a 420px component exceeds its 328px parent by 92px. Compare the finding with a developer’s correction. Findings are delivered through a GitHub Check and job summary.

acme/storefront #248ILLUSTRATIVE PULL REQUEST
OPEN PULL REQUEST

Refine checkout summary

Tailwind CSS exampleMergeRay · Scanning
Scanning source constraints
Layout riskOverflow risk
An opened pull request starts a source review.Illustration · Partial Tailwind support · No automatic fix.
Explore how source becomes evidence

FOR PUBLIC REPOSITORIES

Public code.
Free reviews.

Hosted responsive layout review is free for public repositories. Pro for private repositories is $10 USD per developer per month.

Open clients
Inspect the CLI, Action and public contracts.
Hosted analysis
The engine stays private for both public and private repos.
A clear starting scope
Same-repository PRs first. Fork PR analysis is not supported by the current Action.
Fair use
Public usage and technical limits apply.

YOUR CODE & ACCESS

Know where
your source goes.

Your source code is processed temporarily for analysis. We do not maintain a permanent copy of your codebase or reuse raw source between reviews.

SOURCE → EVIDENCEMR / 01
01

Open clients. Private engine.

Inspect the CLI, GitHub Action and public contracts. Analysis runs on the hosted MergeRay engine; it is not an offline analyzer.

02

Source is sent for analysis.

Clients submit selected committed files and bounded Git metadata at exact revisions over authenticated HTTPS. Metadata can include file paths and commit information.

03

Access has to be authorized.

Installing a client does not grant hosted access. The Action uses an authorized workflow identity, with separate GitHub permissions for publishing Checks and summaries.

Read source processing & retention

BEFORE YOU START

A few things
worth knowing.

A clear scope, an understandable result and a review you can question.

Explore pricing
Do I need a preview URL or browser setup?

No. Supported source review works from committed code, without deploying your application, launching Chromium or logging into your app. It does not replace testing the running application.

Is MergeRay free for public repositories?

Yes. Hosted review is free for public repositories and paid for private repositories. Pro is $10 USD per developer per month, with no monthly review quota or per-review charges. Public usage and technical limits apply.

What happens when the analysis is uncertain?

The result includes its coverage and limitations. Incomplete analysis is not presented as an all-clear. A supported finding can still be reported even when other parts of the review are inconclusive.

Does it automatically fix my code?

No. MergeRay provides findings, source locations and supporting evidence. You review and change the code. Automatic repairs and AI explanations are outside the first public release.

Can I connect my repository today?

Yes. Sign in with GitHub, connect the repositories you choose and follow the quickstart. Source review access is enrolled per repository.