Evidence approval

The EVIDENCING stage requires human review that quality evidence is acceptable before production promotion. LaneSync tracks review and merge state separately and blocks DEPLOYMENT until the evidence pull request is merged on GitHub (when requires_evidence_approval is enabled).

What gets approved

Item	Source
Test evidence	CI upload via `/api/evidence/upload`
Test reports	JUnit and HTML artifacts
Evidence PR	Created when evidence is ready for review

Review satisfies evidencing.required_reviewers in sdlc.yaml. Merge satisfies the EVIDENCING exit gate when deployment.requires_evidence_approval is true.

Configure reviewers

evidencing:
  required_reviewers:
    min_approvals: 1
    teams:
      - engineering-leads

Field	Description
`min_approvals`	Minimum approving reviews required before merge
`teams`	GitHub team slugs whose members can approve

Map teams to your org’s release managers or engineering leads. LaneSync checks GitHub team membership for eligible approvers.

Find your pending reviews

Open My reviews for verified Eligible for me reviews, or choose All workspace reviews to inspect eligibility that is unknown or unavailable. Each entry shows the live reviewer policy and merge consequences. Review evidence PR opens the in-app pull request panel; Release readiness opens the release’s quality and gate details. An empty personal list is not proof that no review is pending. Missing team access or unsupported policy is shown as unknown. Merge alone is not confirmation of production deployment. See Reviews and release history.

Review and merge workflow

CI uploads evidence

Release branch CI completes and POSTs evidence. Uploaded quality reports appear in milestone stage details (dev and staging).

Review stage details

Open the milestone on lanesync.dev. The EVIDENCING section lists artifacts and PR status (Awaiting review, Approved · merge pending, or Merged).

Approve and merge the evidence PR

Use the in-app pull request panel (release readiness, My reviews, or the evidence card) to:

Approve — submits your GitHub review via OAuth
Merge — merges on GitHub (App token with user or setup PAT fallback where configured)

You can also approve and merge directly on GitHub; webhooks and sync refresh LaneSync state.

Stage advances

When the evidence PR is merged and other gates pass, LaneSync advances the milestone to DEPLOYMENT.On release-branch repos, LaneSync promotes the latest {milestone-title}-rc-* tag (for example v1.0.0-rc-83a4334) to a production tag matching the milestone title (v1.0.0) after merge, not on approve-only.

API

Session-authenticated users can approve or merge programmatically:

GET  /api/pull-requests/:owner/:repo/:number
POST /api/pull-requests/:owner/:repo/:number/reviews   { "context": { "kind": "evidence", "milestoneId": "..." } }
POST /api/pull-requests/:owner/:repo/:number/merge     { "context": { "kind": "evidence", "milestoneId": "..." } }

Legacy approve-only endpoint (does not advance stages or merge):

POST /api/milestones/:id/approve

Deploy gate dependency

Production deploy workflows should check the deploy gate before promoting:

deployment:
  requires_evidence_approval: true

When true, the deploy gate remains closed until the evidence PR merge is recorded.

Get Started

Concepts

Guides

Dashboard

Reference

Enterprise

Evidence approval

What gets approved

Configure reviewers

Find your pending reviews

Review and merge workflow

API

Deploy gate dependency

​What gets approved

​Configure reviewers

​Find your pending reviews

​Review and merge workflow

​API

​Deploy gate dependency

What gets approved

Configure reviewers

Find your pending reviews

Review and merge workflow

API

Deploy gate dependency