How to Add a Git Reporting Tool to Your Repository

Adding a git reporting tool to your repository takes less time than making a sandwich. No, really. No YAML configs, no CI/CD pipelines, no asking DevOps for permission. Just connect, configure, and go.

Here's the full walkthrough.

Before You Start

You'll need:

• A repository on Github, Gitlab, or Bitbucket
• Admin or owner access to the repository (for connecting via OAuth)
• A Slack workspace or email address for receiving reports

That's it. No code access needed. No installation inside your repo. The tool reads activity through your git provider's API.

Step 1: Sign Up and Connect Your Git Provider

Head to app.gitmore.io and sign up. You can use your Github, Gitlab, or Bitbucket account directly. OAuth handles the connection. No passwords to share, no tokens to manage.

Step 2: Pick Your Repositories

Once connected, you'll see a list of your repositories. Select the ones you want to track. You can start with one and add more later, no commitment.

Most teams start with their most active repo to see the value immediately. If you're not sure, pick the one that gets the most PRs per week.

Step 3: Configure Your Schedule

Choose how often you want reports:

• Daily: great for active teams who want to stay on top of things
• Weekly: perfect for managers who want a high-level summary without the noise

You can always change this later, and you can set different schedules for different repositories.

Step 4: Choose Your Delivery Channel

Reports can be delivered to:

• Slack: drops the report right into a channel of your choice. Great for team visibility.
• Email: lands in your inbox with a clean HTML format. Perfect for stakeholders who aren't on Slack.

You can set up both if you want. For example, daily Slack reports for the engineering team and a weekly email summary for leadership.

Step 5: Your First Report

Once configured, Gitmore will scan your repository activity and generate your first report. Depending on when you set it up, you might get one the same day or the next morning.

The report includes:

• A summary of all commits and PRs in the period
• Per-developer activity breakdown
• AI-categorized work (bug fixes, features, refactors, etc.)
• PR review status and merge activity

Advanced: Custom Automations

Once you're comfortable with the basics, you can set up custom automations. These let you trigger reports or notifications based on specific events, like when a PR has been open for more than 3 days, or when a developer pushes to a protected branch.

Think of it as "if this, then report", but for your git activity.

Works with All Three Platforms

Whether your team uses Github, Gitlab, or Bitbucket, the setup process is the same. Connect via OAuth, pick repos, set your schedule, and start receiving reports. All three platforms are supported equally.

If your team uses multiple platforms (it happens more than you'd think), you can connect all of them and get unified reports across providers.

No YAML. No CI/CD. Just Connect.

The whole point is that this shouldn't feel like setting up infrastructure. You don't need to modify your repository, add config files, or set up webhooks manually. It's a SaaS tool that reads your existing git activity and turns it into reports.

If you want to understand more about why teams use git reports and what you can do with them, check out our guide on tracking developer activity.