Auto-Merge for Contributors in LinearB
Auto-Merge ensures cleaner data , eliminates duplicates, and provides a more accurate view of developer activity across the platform. Auto-Merge Process. Each day, LinearB scans for contributors who…

Auto-Merge ensures cleaner data, eliminates duplicates, and provides a more accurate view of developer activity across the platform.
Auto-Merge Process
Each day, LinearB scans for contributors who meet at least one of the following criteria and merges them automatically:
✔ Matching Email – Contributors with the same email across Git or PM tools are merged automatically.
✔ Matching Provider ID – Contributors with identical provider IDs (e.g., GitHub, GitLab, Bitbucket, Jira, or Azure DevOps) are merged to maintain consistency.
Auto-Merge runs automatically in the background with 100% accuracy, ensuring data integrity without requiring manual intervention. Since the process is designed for high accuracy, it remains permanently enabled, but admins have full control and can manually unmerge contributors if needed.

Reviewing and Managing Merged Contributors
Merged contributors can be reviewed in the People & Teams section under Company Settings. If a merge is incorrect, admins can manually unmerge contributors to restore individual records.
Because Auto-Merge runs daily, it continuously keeps contributor data up to date, reducing duplicate entries and improving reporting accuracy across the platform.
By ensuring a unified contributor record, Auto-Merge improves data reliability, enhances team insights, and eliminates redundant data, giving teams a clearer view of developer contributions across the organization.
How did we do?
Configuring SAML SSO with GSuite