centrailYancy Collective LLC
Sign inSign up
Reading the numbers / How team numbers work

How team numbers work

What a team's Overview counts, what it never does, and what the GitHub App changes.

Your personal Overview counts everything your own devices sync — every repository and folder, assigned to a project or not — plus the chat-app exports you import. A team's Overview counts far less, on purpose: only what each member chose to share with that team.

What a team number includes

  • Repositories members share. Each member picks, per repository, whether their usage in it counts for the team (Settings → Team → Your sharing), and the repository has to be on the team's list. It counts from the day they shared it, or from an earlier date they chose. Their other repositories and folders never count.
  • Work assigned to team projects, for members on the earlier sharing setup. Members who joined before October 2026 keep their narrower disclosure until they switch: only work they assign into the team's projects counts, from the day they joined unless they included earlier history. These rows show as projects beside the repositories.

A member is on exactly one of the two, so nothing counts twice. Chat-app imports never count toward a team, and only current members count: leaving removes a member's usage from every team view, including earlier periods.

Commits and cost per commit

A team's commits are its members' commits in those same shared repositories (or assigned projects), from the CLI's git attribution on each member's machine — not only pull requests, and not only merged work. Cost per commit is the members' estimated allocation of that usage to those commits.

What the GitHub App changes

It adds no tokens, removes none, and never decides what counts: installing it shares nobody's usage. When a member has linked their GitHub account and GitHub saw them push or merge a commit on the same branch after the agent work, the spend matched to that commit can read "matched to forge commits" instead of "self-reported" — in the team's cost per commit as in their own. The amount is still an estimate.

Per-member numbers

A team's admins choose who sees per-member breakdowns: everyone, admins only, or no one — then the team sees totals alone. See Privacy → Teams for exactly what a team can and can never see.