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

​
Onboard your organization

1

Sign in to LaneSync

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

Install the LaneSync GitHub App

From the setup wizard, install the LaneSync GitHub App on your GitHub org 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

Run the repo setup wizard

LaneSync discovers your repositories and prompts the repo setup wizard for any new repository.The wizard:
  • Detects your primary language and CI template
  • Bootstraps sdlc.yaml at the repo root
  • Pushes GitHub Actions workflow templates
  • Creates branch protection rulesets (full tier)
Choose trunk-based or release-branch workflow during setup.
4

Create your first milestone

In GitHub, create a milestone (e.g. v1.0.0) with 2–3 issues linked to it.Alternatively, create the milestone from the LaneSync dashboard using Create milestone.

​
Advance through the pipeline

1

PLANNING → DEVELOPMENT

Assign all milestone issues to team members. LaneSync blocks advancement until every issue has an assignee.
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.