# I've created a website to track the team's activity

DevFeed: [I've created a website to track the team's activity](<https://devfeed.tech/articles/i-ve-created-a-website-to-track-the-team-s-activity-5623.md>)

Original publisher: [Read original article](<https://clickhouse.com/blog/velocity>)

Author: Alexey Milovidov

Published: 2025-11-10T00:00:00Z

Content type: article

Language: en

Sources: [ClickHouse Blog](<https://devfeed.tech/sources/clickhouse-blog.md>)

Topics: [GitHub Issues](<https://devfeed.tech/topics/github-issues.md>), [Database](<https://devfeed.tech/topics/database.md>), [Bun](<https://devfeed.tech/topics/bun.md>), [elasticsearch](<https://devfeed.tech/topics/elasticsearch.md>), [PyTorch](<https://devfeed.tech/topics/pytorch.md>), [Chromium](<https://devfeed.tech/topics/chromium.md>)

Tags: [clickhouse](<https://devfeed.tech/tags/clickhouse.md>), [database](<https://devfeed.tech/tags/database.md>), [developer-productivity](<https://devfeed.tech/tags/developer-productivity.md>), [github](<https://devfeed.tech/tags/github.md>), [github-issues](<https://devfeed.tech/tags/github-issues.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [pull-requests](<https://devfeed.tech/tags/pull-requests.md>), [sql](<https://devfeed.tech/tags/sql.md>)

## AI overview

The article introduces a website for comparing GitHub repository activity metrics and argues that commits, pull requests, and issue counts should be interpreted as secondary signals rather than productivity targets.

## Source excerpt

Initially, I wanted to make a single report to incentivise for looking at and resolving GitHub issues. But I'm greedy, so in the end it appeared to be a website where you can compare various metrics on team activities across GitHub repositories.