Reporting

Overview

The Reporting page lets you control how contributors appear across GitVelocity -- dashboards, leaderboards, and exported reports. Use it to set readable display names, hide inactive contributors, and remove bot accounts from your data.

Display Names

By default, GitVelocity uses GitHub usernames to identify contributors. On the Reporting page, you can set a custom display name for any contributor.

Setting display names to first names (or first name + last initial) makes dashboards and reports easier to read, especially when sharing with non-technical stakeholders who may not recognize GitHub handles.

Display names apply everywhere in GitVelocity: dashboards, leaderboards, contributor profiles, and exported data.

Hiding Contributors

If someone leaves the team or moves to a different project, you can hide them from active reports. Hidden contributors:

• Don't appear on dashboards or leaderboards
• Don't show up in filtered views or exports
• Retain all historical scoring data -- nothing is deleted

This keeps your active views focused on current team members without losing historical context. You can unhide a contributor at any time to restore their visibility.

Hiding Bots

Bot accounts that commit code -- Dependabot, Renovate, CI bots, and similar automation -- can clutter reports if they aren't filtered out. Go to Settings > AI Scoring > Bot Exclusion to manage which bots are excluded from velocity metrics. The platform ships with sensible defaults (Dependabot, Renovate, GitHub Actions, Snyk, Codecov) and auto-detects bots in your repos. You can add custom bots like Jenkins or other CI usernames.

Excluded bots are filtered from both scoring and team display. Use the Reporting page to additionally hide specific contributors who aren't bots.

If bot-authored PRs are still being scored, consider also adding PR exclusion filters to skip scoring them entirely.