Auto-Merge for Contributors in LinearB
Automatically unify contributor identities across Git and PM tools to keep attribution accurate and avoid duplicate contributors in reporting and billing.
Auto-Merge in LinearB ensures clean, accurate contributor data by automatically unifying identities across Git and project management tools—eliminating duplicates and improving visibility into developer activity.
Summary
- Auto-Merge automatically consolidates duplicate contributor identities.
- Merging is based on matching emails or provider IDs.
- The process runs daily and requires no admin configuration.
- Admins can manually unmerge contributors if needed.
Overview
Auto-Merge consolidates contributor records across connected systems such as GitHub, GitLab, Bitbucket, Jira, and Azure DevOps.
Contributors often appear multiple times due to different email addresses, usernames, or provider identities. Auto-Merge resolves this by maintaining a single, unified contributor record.
This improves:
- Accuracy across dashboards and reports
- Clarity in team- and individual-level insights
- Data integrity for planning, billing, and decision-making
Auto-Merge Logic
Each day, LinearB scans contributor records and automatically merges entries that meet at least one of the following criteria:
- Matching Email – Contributors with the same email address across Git or PM tools are merged.
- Matching Provider ID – Contributors with identical provider IDs (for example, GitHub, GitLab, Bitbucket, Jira, or Azure DevOps) are merged.
Auto-Merge is designed for high accuracy and runs automatically in the background. Because of this reliability, it remains permanently enabled.
Reviewing and Managing Merged Contributors
You can review merged contributors in Settings → Company Settings → People & Teams.
If a merge is incorrect, admins can manually unmerge contributors to restore separate records.
Because Auto-Merge runs daily, it continuously keeps contributor data accurate and up to date—reducing duplication and improving reporting across LinearB.
Why this matters
By maintaining a unified contributor identity, Auto-Merge:
- Prevents inflated contributor counts
- Improves accuracy in billing and licensing
- Ensures developer activity is attributed correctly
- Provides clearer insights into team performance
The result is a cleaner data model and more trustworthy engineering metrics across your organization.
How did we do?
Managing Users in LinearB
