
Table of contents
Comments in GitHub represent a major part of collaborative engineering work. Developers discuss changes, review code, clarify decisions, and coordinate through comments on pull requests and issues. TeamScore ingests high-level comment metadata so teams can understand when engineers participate in review and discussion without exposing any comment content.
What TeamScore Receives
TeamScore receives GitHub webhook events for:
- Comments on pull requests
- Comments on issues
- General discussion comments within PR threads
Each comment event includes:
- Comment author (GitHub username)
- Timestamp
- The PR or issue the comment belongs to
TeamScore does not ingest the comment text itself or any code diff information.
How Comments Appear in TeamScore
TeamScore displays comment activity as individual metadata-only events tied to the associated pull request or issue.
Comment entries show:
- The repository
- The PR or issue title
- The fact that a comment was added
- The timestamp of the activity
This provides clear visibility into review participation and collaboration patterns while respecting privacy and code security.
Comments from unmapped GitHub users do not appear in TeamScore.
Role Within GitHub Activity
Comments complement other GitHub events:
- Commits show what work was done
- Pull Requests show what changes are being proposed
- Comments show how engineers collaborate around those changes
Together, these activities help teams understand not just what was built, but how collaboration is happening.
Data Details and Requirements
TeamScore does not ingest comment body text or diff comments.
Only metadata supplied by GitHub is used.
Comments appear only after the integration is installed.
User mapping is required for attribution.
TeamScore does not ingest code review approval states or requested-changes text.
Next Steps
For issue-level activity, see GitHub Issues.
For pull request lifecycle activity, see GitHub Pull Requests.
For configuration steps and permissions, see GitHub Setup.
For a platform-level explanation of GitHub activity, see GitHub Overview.
