Skip to main content
Get from zero to your first governed release on the hosted LaneSync SaaS at lanesync.dev.
This guide covers the cloud product. For Docker Compose or self-hosted deployment, see Enterprise self-hosting.

​
Prerequisites

  • A GitHub account
  • Org admin access (or permission to install GitHub Apps on your account)
  • At least one repository to track

​
Connect and configure your workspace

1

Sign in to LaneSync

Open lanesync.dev and click Sign In.LaneSync uses GitHub OAuth. If you belong to multiple organizations, you will see a workspace picker after authentication.
2

Install the LaneSync GitHub App

Install the LaneSync GitHub App on your GitHub organization or personal account.Choose repositories to grant access — you can add more repos later. LaneSync needs webhook and repository permissions to sync milestones, PRs, and workflow runs.
Use the full tier GitHub App if you want LaneSync to create branch rulesets automatically. See Install the GitHub App for tier comparison.
3

Choose organization or repository setup

Open Orgs & Repos. For an organization, choose Configure organization to keep shared configuration in <org>/.github/sdlc.yaml and LaneSync-managed SDLC rulesets in GitHub organization settings. The wizard reviews which repositories the GitHub App can access and whether you allow supported repository customization. See Configure an organization for permissions and coverage.Choose Configure repository for an independent repository, or when using a personal account. That path stores sdlc.yaml at the repository root and LaneSync-managed rulesets in its GitHub repository settings. The repository wizard also helps select language and managed workflows.In either path, review the branch model, checks, approvals, and quality requirements before applying setup. GitHub App access and permissions determine which actions LaneSync can complete.
4

Create your first release

In Releases, select New release. Follow Define release → Scope → Review to create a milestone such as v1.0.0 or select an existing open milestone, then choose or create the issues shipping in it.Complete the applicable setup before creating a release. Saved configuration and a merged setup PR alone do not prove protection is active.

​
Advance through the pipeline

1

PLANNING → DEVELOPMENT

Open Scope & owners and assign issue owners in LaneSync. Missing ownership blocks advancement when required by the configured planning policy.
2

DEVELOPMENT → TESTING

Merge PRs that close milestone issues. Cut a release branch (e.g. release/v1.0.0) unless you configured trunk-based releases.
3

TESTING → EVIDENCING

Wait for required CI checks (from sdlc.yaml) to pass on the release branch. LaneSync reads check names live from GitHub.
4

EVIDENCING → DEPLOYMENT

Approve the evidence PR from the dashboard or GitHub. Required reviewers are configured in sdlc.yaml.
5

DEPLOYMENT → DEPLOYED

Trigger production deploy after the deploy gate passes. Promotion is manual by default.

​
What you should see

The dashboard auto-syncs every 60 seconds. Click Refresh or wait for a real-time push after webhook events.

​
Next steps

Advance a full release

Detailed walkthrough of each stage gate.

Configure sdlc.yaml

Customize checks, artifacts, and reviewers per stage.

Update LaneSync Workflows

Refresh managed GitHub Actions templates after bootstrap.