Skip to main content
Use My reviews to inspect evidence awaiting sign-off and History to revisit recorded shipped releases.

​
Find evidence reviews

Eligible for me shows reviews for which live GitHub checks confirm your eligibility. All workspace reviews also includes reviews with unknown or ineligible status. An empty personal list does not prove there are no workspace reviews. Each review shows its repository, release, evidence PR, reviewer eligibility, effective policy and approval consequences. LaneSync checks the PR state, your repository access and any configured reviewer-team membership. PR authors cannot approve their own PRs; draft, closed and merged PRs are not actionable approvals.
Unavailable GitHub access or unsupported policy is shown as unknown, rather than permission to approve. GitHub still applies its own review and branch rules.
Open Release readiness to inspect quality and release evidence. Check current eligibility opens the release for a fresh policy check before approval; View evidence on GitHub opens the original PR. See Evidence approval for the release’s approval action.

​
Check what approval means

The review panel reads live sdlc.yaml to show required approvals, reviewer teams, deployment target, promotion mode and whether deployment requires evidence approval. Review the repository’s automation before approving: these policy fields do not verify every workflow trigger, and approval alone does not confirm production deployment. If the review list cannot refresh, any retained details are explicitly marked as previously loaded. Verify current permissions and PR state before acting.

​
Inspect release history

Open History, select a repository if needed, then set From (UTC) and Through (UTC). Both dates are inclusive. Records without a timestamp are excluded when a date filter is applied. The recorded deployment date comes from the latest successful production deployment when one exists. Otherwise, LaneSync uses a recorded transition to DEPLOYED. Dates represent when LaneSync stored the event, rather than the latest milestone edit. A deployed record may have an unknown date if neither event timestamp is available. Open a release record to inspect its activity, candidate and available deployment links. Successful production records take precedence over stage transitions; successful staging or failed production runs do not establish a shipped release. Approval identity and time appear only when an approval is recorded. These fields reflect the stored evidence record, not an immutable snapshot taken at deployment. A deployed stage or stale approver name alone is not approval evidence.

Release readiness

Inspect the candidate, stage gates and next action.

Evidence approval

Configure reviewers and understand approval behavior.