Table of contents
GitHub Integration Overview
The GitHub integration brings engineering activity into WorkSights using metadata from GitHub's webhook framework. WorkSights receives push events, pull request actions, comments, and issue activity in real time, giving teams clear visibility into how development work unfolds without accessing any source code.
For connection steps, see GitHub Setup.
What WorkSights Receives
WorkSights 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
If a commit message includes a hashtag-style duration value such as #45m, #2h, or #1h30m, WorkSights reads this through the GitHub API and associates that duration with the commit. This gives engineering teams passive time attribution without requiring developers to log time manually.
Source code, diffs, file contents, and repository data are never received or stored.
How GitHub Activity Appears
WorkSights 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 on the user's timeline, followed by the individual commits included in that push. Commits use their original timestamps so WorkSights can reconstruct the true sequence of development effort, even when work was completed offline or batched before pushing.
Pull requests and issues appear with their open, edit, sync, close, and comment activity. Comments appear as metadata-only entries linked to the corresponding GitHub object.
Integration Page Overview
The GitHub integration page contains three tabs:
- Overview: connection information and GitHub App installation details
- Users: manual mapping of GitHub usernames to WorkSights users
- Connections: GitHub App scope and repository selection
GitHub identifies users by username rather than email. Manual mapping ensures accurate attribution across internal developers, external contributors, and contractors.
Data Access and Privacy
WorkSights receives metadata only: commit messages, pull request titles, issue metadata, and comment metadata. Source code, diffs, repository content, and file-level data are never received or stored. All data follows GitHub's permission model and is limited to the repositories selected during GitHub App installation.
Troubleshooting
If GitHub activity is not appearing as expected:
- Confirm the WorkSights GitHub App is installed on the correct GitHub organization and repositories.
- Check that the affected user is mapped to their GitHub username in the Users tab. GitHub uses usernames, not email addresses, for attribution.
- If a repository was added after the initial installation, update the GitHub App settings to include it.
- For persistent issues, contact support via the in-app chat.