Auto-Monitoring for Git Reporsitories

TL:DR

• Automatically include new repositories as they are created or discovered.
• Use regex-based rules to control inclusion and exclusion.
• Supports private, public, and internal repositories.
• Requires sufficient Git token permissions to detect repositories.

---

Overview

Repository Auto-Monitoring automatically tracks newly created or discovered repositories connected to your Git provider, ensuring they are added to LinearB without manual setup. This helps keep metrics complete as your organization grows.

LinearB supports auto-monitoring for GitHub, GitLab, Bitbucket Cloud, and Azure DevOps (ADO), across private, public, and internal repositories.

Auto-Monitoring for Bitbucket Cloud and Azure DevOps is currently available under feature flags (FFs) - Please contact support for assistance.

Supported Auto-Monitoring Scenarios

Repository auto-monitoring is supported for the following Git providers and deployment models:

Git Provider	Deployment Type	Auto-Monitoring Supported
GitHub	Cloud	✅ Available
GitLab	Cloud / Self-Managed	✅ Available
Bitbucket	Cloud	✅ Available
Bitbucket	Server (non-OPA)	❌ Unavailable
Azure DevOps	Cloud	✅ Available

---

Before you begin

Prerequisites: 

• You must be a Company Admin in LinearB.
• Your Git integration token must have access to the repositories you want to monitor.

• Auto-Monitoring for Bitbucket Cloud and ADO require a feature flag to be enabled. Please contact support for assistance.

---

Configure repository auto-monitoring

1. Access Monitoring Rules

   1. Go to Settings → Company Settings.
   2. Open the Git tab.
   3. Click the three-dot menu next to Add Repositories.
   4. Select Monitoring Rules.

   UI Availability: If you do not see Monitoring Rules, auto-monitoring may not be supported for your Git provider or deployment type (for example, Bitbucket Server (non-OPA)).

2. Define monitoring rules

   1. Enter a regex pattern to include repositories.
      • To include all repositories, use .*.
   2. Optionally add exclusion rules (for example, documentation repositories).

3. Verify token access

   • Ensure your Git token can access the repositories being monitored. Repositories without permission will not be detected.

4. Select repository visibility

   Choose which repository types to monitor: private, internal, and/or public.

   

5. Configure organizational scope (GitHub only)

   Define which organizations are included using regex or manual selection.

6. Define inclusion and exclusion rules

   • Include repositories using a regex in the Include field.
   • Exclude repositories using a regex in the Exclude field.
   • Example:
     • ^test* excludes repositories starting with test.

7. Select organizations

   1. Use regex (for example, .* for all orgs, ^linear- for orgs starting with “linear-”).
   2. Or manually select organizations from the list.

8. Enable Auto-Monitoring

   Ensure the Auto monitored toggle is enabled.

9. Click Save to apply your configuration.
    

Important notes

• UI availability: If auto-monitoring is not supported for your Git provider or deployment type, the Monitoring Rules option will not appear in the integration menu. This behavior is expected and does not indicate a misconfiguration.
• New repository sync: Allow up to 24 hours for newly added repositories to appear.
• New organizations: GitHub organizations added later must be manually selected in monitoring rules.
• Regex precision: Carefully define exclusion rules to avoid monitoring unintended repositories.