Oobeya Docs
  • GETTING STARTED
    • Welcome to Oobeya!
    • Get Started with Oobeya
    • Playground: Live Demo
    • Oobeya Quick Onboarding Guide
  • TEAM INSIGHTS & SYMPTOMS
    • Symptoms Catalog
      • S1- Recurring high rework rate
      • S2- Recurring high cognitive load
      • S3- High weekend activity
      • S4 - High Code Review Time
      • S6- High technical debt on Sonar
      • S7- High vulnerabilities on Sonar
      • S8- High code quality bugs on Sonar
      • S9 - Unreviewed Pull Requests
      • S10 - Lightning Pull Requests
      • S11 - Oversize Pull Requests
      • S12- High Lead Time For Changes (DORA)
      • S13- Low Deployment Frequency (DORA)
      • S14- High Change Failure Rate (DORA)
  • SECURITY
    • 🔐Security at Oobeya
    • Oobeya Managed SaaS
  • INSTALLATION
    • 🐳Oobeya Docker Installation Tutorial & Requirements
    • 🐳Oobeya Version Upgrade For the docker-compose Installations
    • 🐳HTTPS Configuration For Docker Installations
  • PRODUCT DOCS
    • ⭐Oobeya Release Notes
      • 🎁Oobeya 2024 Q1 - Release Notes
      • 🎁Oobeya 2023 Q4 - Release Notes
      • 🎁Oobeya 2023 Q3 - Release Notes
      • 🎁Oobeya 2023 Q2 - Release Notes
      • 🎁Oobeya 2023 Q1 - Release Notes
      • 🎁Oobeya Nov & Dec '22 Updates
      • 🎁Oobeya September 2022 Updates
      • 🎁Oobeya August 2022 Updates
      • 🎁Oobeya July 2022 Updates
      • 🎁Oobeya June 2022 Updates
      • 🎁Oobeya Apr & May 2022 Updates
      • 🎁Oobeya March 2022 Updates
      • 🎁Oobeya Feb 2022 Updates
      • 🎁Oobeya Jan 2022 Updates
      • OOBEYA-2.0.8 - Release Notes
      • OOBEYA-2.0.4 - Release Notes
      • OOBEYA-2.0.0
      • OOBEYA-1.4.6
      • QAD-1.0 - 1.4
    • ▶️Product Tour
    • ❇️Metrics List
    • ☀️Developer Experience Metrics
  • INTEGRATIONS
    • Integration Catalog
      • SCM & CI/CD Integrations
        • Azure DevOps Integration
        • Bitbucket Cloud Integration
        • Bitbucket Server Integration
        • GitHub Integration
        • Step-by-Step Integration Instructions for the Oobeya GitHub Application
        • GitLab Integration
        • Jenkins & Cloudbees Integration
        • Octopus Deploy Integration
        • TeamCity Integration
      • Quality & Security Integrations
        • SonarQube Integration
        • SonarQube Cloud Integration
        • Veracode Integration
      • Project Management Integrations
        • Jira Cloud Integration
        • Jira Server Integration
      • APM / Monitoring Integrations
        • AppDynamics Integration
        • Azure Application Insights Integration
        • Dynatrace Integration
        • Elastic APM Integration
        • New Relic Integration
        • Sentry Integration
    • Installing An Addon
    • Adding A New Data Source
    • Updating and Deleting Data Sources
  • ADMINISTRATION
    • User Management, Single Sign-On, Auth Settings
      • Microsoft Entra (Azure AD) Integration
      • LDAP / Active Directory Integration
      • Importing a New User From LDAP / Active Directory
      • Bulk User Import in Oobeya Using CSV
      • Adding a New User
      • Deactivating a User
      • Understanding Roles in Oobeya
    • License Management
      • Updating The License Key
  • DEVELOPMENT ANALYTICS - GITWISER
    • Git Analytics - Metric Definitions
      • Coding Impact Score
      • Impact Ratio (team-level)
    • Setting Up Development Analytics And DORA Metrics
    • Git Analytics Exclusions
    • Setting Automated Reanalyze For Gitwiser
    • Deployment Analytics (DORA Metrics)
    • Merging Contributor Accounts
  • DORA Metrics
    • DORA Metrics Introduction
      • Lead Time For Changes (LTC)
      • Deployment Frequency (DF)
      • Change Failure Rate (CFR)
      • Mean Time To Restore Service (MTTR)
    • Failure Detection (For Change Failure Rate & MTTR)
    • How To Calculate DORA Metrics for GitHub
    • Updating Team Scorecard configuration to display DORA Metrics
    • How To Start Deployment Analytics (DORA Metrics) For An Existing Gitwiser Analysis
  • Project Analytics - AgileSpace
    • Agile Analytics - Metric Definitions
    • Agile Board Analytics Intro
    • Starting an Agile Board Analytics
    • Board Overview
    • Sprint Reports
    • Update the Agile Board Analytics
  • QUALITY ANALYTICS
    • Total Code Quality Index (TCQI)
  • Guides
    • Azure DevOps Guides
      • How To Calculate DORA Metrics for Azure DevOps
      • Best practices for integrating Oobeya with Azure DevOps Scrum Boards
  • PROFILES
    • Introduction
    • Adding A Profile
    • Developer Scorecard
    • Adding A Related Account Information To Oobeya Profile
  • Team Health
    • Adding A Team
    • Team Scorecard
    • Project Analytics (Scrum Teams) Widget
  • Test Quality Report Widget
  • CUSTOM DASHBOARDS
    • Adding A New Dashboard
    • Adding A New Widget
    • Updating And Deleting Widgets
    • Adding Jira Sprint Progress Widget
    • Adding Jira Board Metrics Widget (Metrics With JQL)
  • SUPPORT
    • Support Request Workflow
    • Customer Success & Support Guide
Powered by GitBook
On this page
  • 1- Global Exclusions (Admin Setting)
  • 2- Repository-level Exclusions
  • 3- Commit-level Exclusions
  • Conclusion

Was this helpful?

  1. DEVELOPMENT ANALYTICS - GITWISER

Git Analytics Exclusions

PreviousSetting Up Development Analytics And DORA MetricsNextSetting Automated Reanalyze For Gitwiser

Last updated 1 month ago

Was this helpful?

Gitwiser allows you to fine-tune your analytics by excluding unnecessary files, directories, or specific commits from the analysis. This ensures metrics are focused on meaningful contributions. Exclusions can be applied at a global level, repository level, or commit level.

Example
Scope

**/*.xml

Excludes all xml files from Gitwiser analysis.

**/data.json

Excludes all data.json files from Gitwiser analysis.

**/*sample*/**

Excludes directories that include "sample" in their folder name.


1- Global Exclusions (Admin Setting)

Admins can define exclusion patterns that apply to all repositories across the platform.

  • Navigate to: Administration → Admin Settings → Gitwiser & DORA Metrics → Git Analytics

  • In the Exclusion List, add glob patterns such as: **/.aac → excludes all .aac files **/.apng → excludes all .apng files

  • Toggle Reset Existing Analyses if you want Gitwiser to reanalyze existing data based on new patterns.

📌 These exclusions are global and affect all repos.


2- Repository-level Exclusions

You can configure exclusion patterns for a specific repository.

If you're creating a new analysis:

  • During setup, you'll see the Advanced Settings step

  • Add your file exclusion patterns there (e.g., **/*.xml, **/*sample*/**)

If the analysis already exists:

  • Go to: Gitwiser & DORA Metrics → select the repository → Git Analytics

  • Click the three dots (⋯) in the top-right corner of the Git Analytics page

  • Select Update Analysis

  • You'll be able to edit exclusion patterns here


3- Commit-level Exclusions

Specific commits can also be manually excluded from analytics.

  • Navigate to: Gitwiser & DORA Metrics → select the repository → Git Analytics

  • Scroll to the Contributions During the Selected Period section

  • Click Exclude next to the commit(s) you want to exclude

  • Excluded commits appear in the Excluded Commits section at the bottom

🧠 Useful for filtering out noise like formatting commits, reverts, or merge commits.


Conclusion

Using Git Analytics Exclusions effectively helps ensure your metrics reflect meaningful contributions by filtering out noise like binary files, test data, or irrelevant commits. Whether you're applying exclusions globally, per repository, or at the commit level, these tools give you full control over the scope of your analysis in Gitwiser. For best results, review and refine your exclusion patterns regularly based on your team's workflow.