Git Analytics Exclusions

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.

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.