Skip to main content
The EVIDENCING stage requires human approval that quality evidence is acceptable before production promotion. LaneSync tracks approval state and blocks DEPLOYMENT until reviewers sign off.

What gets approved

Approval satisfies evidencing.required_reviewers in sdlc.yaml and, when configured, deployment.requires_evidence_approval.

Configure reviewers

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

Approval workflow

1

CI uploads evidence

Release branch CI completes and POSTs evidence. Required artifacts appear in milestone stage details.
2

Review stage details

Open the milestone on lanesync.dev. The EVIDENCING section lists artifacts and approval status.
3

Approve the evidence PR

Approve via either:
  • LaneSync dashboard — click Approve evidence
  • GitHub — approve the linked evidence pull request
4

Stage advances

When min_approvals is met, LaneSync records approval and advances the milestone to DEPLOYMENT (if all other gates pass).

API approval

Session-authenticated users can approve programmatically:
Useful for automation that integrates with internal change-management systems (with appropriate auth).

Deploy gate dependency

Production deploy workflows should check the deploy gate before promoting:
Production deploy blocked? Verify evidence PR is approved and can_deploy is true. See Troubleshooting.

Audit trail

Evidence approval is recorded with:
  • Approver identity (GitHub user)
  • Timestamp
  • Milestone version and repository
Export quality reports after approval for compliance archives. See Quality scorecards.