Shortcut: Ctrl/Cmd + K

Commitlane documentation

Documentation

Learn how to connect GitHub, GitLab or Bitbucket, read delivery and DORA metrics, forecast tasks and create reports in Commitlane.

Start with a Git connection. Guides for tasks, deployments and incidents are listed below when you need them.

Connect your first repository

  1. Create an account, connect your Git provider in Settings → Integrations and select a repository. Run a sync and check that it finishes successfully.
  2. To view an individual profile, open Profiles and activate the 7-day demo for one developer. No card is required; skip this step if the profile already has access.
  3. Open Dashboard and choose dates and a repository you know. Check daily totals in the table, including days without events.
  4. Open Delivery and check a few pull requests in your Git provider. Compare their creation and merge dates with the metric definition.

Check your first results

  • You know which dates, repository and events a metric includes.
  • You have checked a calculation against the source data and understand what it leaves out.
  • You have a concrete question for the team, such as why a particular pull request waited two days for review.

Where to start

Engineering Manager

How often does each service reach production, and how often do releases fail?

Product Owner

When might the remaining tasks be finished, and how would reducing scope change that date?

Product guides

Dashboard

Team activity at a glance: commits, pull requests, time to merge and review participation for the dates you choose.

Knowledge Map

See who changes code in team repositories, each contributor’s share of commits and the bus factor.

Delivery

Pull request analytics: opened and merged counts, average time to merge, and daily or weekly activity.

DORA Metrics

DORA metrics by service: deployment frequency, time to production, change failure rate and recovery time.

Planning

Forecast project completion from remaining tasks and the team’s pace, with several possible finish dates.

Goals

Development metric targets: desired values, current progress and comparison with selected benchmarks.

Automation (Beta)

Run pull request actions manually, inspect their results and configure reviewer rules. Currently in beta.

Team

Developer commits, pull requests, reviews and technologies, with a history of changes in activity.

Reports

Sprint reports with commits, pull requests, time to merge and automatically flagged changes in metrics.

Custom Metrics

Metrics you define with a formula, plus report templates that you can assemble and run manually.

AI Impact (Beta)

AI assistant usage: accepted suggestions, generated code and comparisons between developer groups. Beta.

Capitalization

Development cost tracking with CapEx and OpEx rules, manual corrections and financial-period reports.

Work Items

Tasks from Jira, Linear and Azure DevOps with statuses, assignees and linked code changes.

Surveys

Developer surveys: questions about tools and working conditions, response collection and results by category.