Skip to main content

Private beta GitHub App

Flock GitHub App

Run synthetic UX reviews against supported pull-request previews and review the results in GitHub.

Flock posts a Preview Gate check and PR summary, with inline comments when a finding can be mapped to changed code.

Evidence-backed by default

Read actionable findings with their supporting evidence. Directional observations are labeled separately and do not block the gate. Confidence alone does not establish a defect; inspect the evidence and verification status before deciding what to change.

How the PR loop works

01

Connect and select repositories

A workspace owner or admin connects GitHub from Settings → Integrations → GitHub and chooses repositories. The GitHub account must have access to the App installation.

02

Configure and activate reviews

Set up a supported preview connection, targets, and personas. Select a saved sign-in for authenticated flows, then activate reviews. Installing the App alone does not start reviews.

03

Choose when reviews run

Use automatic, label-based, or manual review settings. Flock checks the current PR and preview readiness before running; missing preview, sign-in, or usage readiness is reported explicitly.

04

Read the Preview Gate

Review the check, PR summary, and available evidence. Choose advisory or required-compatible conclusions in Flock; configure required checks separately in GitHub.

Artifacts in pull requests

The check below is an abbreviated excerpt from a completed production review on September 27, 2026. Repository and run identifiers are omitted. It shows one result, not a guarantee for other reviews. Advisory mode can publish success, failure, or neutral; required-compatible mode publishes success only for a merge-green result and failure otherwise.

Where inline findings appear

Inline comments are added when a finding maps to changed code.

Findings without a supported mapping remain in the PR summary and Flock review.

Directional observations are labeled separately and do not block the gate.

Completed Preview Gate excerpt

{
  "name": "Flock CI / Preview Gate",
  "status": "completed",
  "conclusion": "success",
  "output": {
    "title": "First PR run captured current UX context",
    "summary": "Verdict: pass\nRun outcome: pr_local_baseline_seeded\nall target baselines resolved\nBlocking findings on first PR run: 0\nWarning findings on first PR run: 0\nNot observed in the latest comparison: 0\nStill present from baseline: 0"
  }
}

GitHub review outputs

  • Flock CI / Preview Gate check
  • PR summary with review status and findings
  • Inline comments for findings mapped to changed code
  • Links to the review and available evidence

Repository configuration

For repositories using v2 review settings, this .flock.yml example sets automatic reviews and a checkout target. Configure preview access, personas, saved sign-in if needed, and review activation separately. YAML overrides repository preferences, workspace preferences, and Flock defaults. Existing v1 repositories keep their current configuration until explicitly migrated; changing the version number alone does not migrate a repository.

version: 2
review:
  mode: automatic
  include_drafts: false
  on_updates: true
github:
  check_conclusion_mode: advisory
targets:
  - key: checkout
    path: /checkout

Bring Flock reviews into your PR workflow

Tell us about your repository, preview setup, and the journeys you want to review. We can confirm private beta access and setup requirements.

Request private beta access