The GitHub integration brings real engineering activity into TeamScore with clarity and precision. TeamScore receives GitHub events in real time-pushes, pull request actions, comments, and issue activity while giving teams a high-fidelity view of how development work unfolds.

Commit timestamps are preserved exactly as they occurred, while push events anchor that work to the moment it was delivered upstream. TeamScore ingests metadata only; your source code never leaves GitHub.

How TeamScore Data Appears in TeamScore

TeamScore displays GitHub activity using GitHub’s object hierarchy. Repositories act as the top-level container, with pull requests, issues, commits, and comments nested underneath.

Pushes appear as discrete events in a user’s timeline, followed by the commits included in that push. Commits use their original timestamps so TeamScore can reconstruct the true sequence of development effort, even when work was completed offline.

Pull requests and issues appear with their open, edit, sync, close, and comment activity, giving teams a clear view into both code changes and review workflows. Comments appear as concise, metadata-only activity linked to the corresponding GitHub object.

Objects TeamScore Receives from GitHub

TeamScore ingests only the metadata GitHub provides through its app webhook model:

• Push events and the commits contained within them
• Pull request events, including open, edit, synchronize, and close
• Review activity, including approvals, change requests, and review comments
• Issue creation and issue comments
• Inline code review comments across pull requests

TeamScore does not ingest code, diffs, file contents, or repository data.

Developers using time notation (# followed by a duration) inside commit messages will have that duration reflected as part of their TeamScore activity.

Integration Page Overview

The GitHub integration page includes:

• Overview Tab — connection information and GitHub App installation details
• Users Tab — manual mapping of GitHub usernames to TeamScore users
• Connections Tab — GitHub App scope and repository selection

GitHub identifies users by username rather than email, so manual mapping ensures accurate attribution across internal developers, external contributors, and contractors.

Data Access and Privacy

TeamScore receives metadata only: commit messages, pull request titles, issue metadata, and comment metadata. TeamScore never ingests or stores source code, diffs, repository content, or file-level data. All data follows GitHub’s permission model and is limited to the repositories selected during GitHub App installation.

Troubleshooting

If GitHub activity does not appear:

• Confirm the TeamScore GitHub App is installed on the GitHub organization and correct repositories.
• Verify that the user is mapped to their GitHub username in the Users tab.
• Ensure the push or comment came from a mapped GitHub identity.
• If a repository was added later, reauthorize or update GitHub App settings to include it.

For connection steps, see the GitHub Setup Guide.

For commit-level activity, see GitHub Commits.

For pull request lifecycle visibility, see GitHub Pull Requests.

For issue-level activity, see GitHub Issues.

For comment-level collaboration activity, see GitHub Comments.