Table of contents
GitHub Commits
Git commits represent the core of a developer's daily work. When developers push commits to GitHub, WorkSights receives structured metadata that reflects both the push event and the individual commits included in it, giving teams clear visibility into engineering activity without accessing any source code.
For connection steps, see GitHub Setup.
What WorkSights Receives
When a developer pushes to GitHub, WorkSights receives:
- The push event, timestamped at the moment of the push
- All commits included in that push, each with their original commit timestamp, commit message, commit identifier, and associated GitHub username
WorkSights does not ingest code diffs, file contents, or changed lines.
How Commits Appear
WorkSights represents push and commit activity in two stages:
The Push appears as a single timeline entry timestamped at the moment the developer pushed to GitHub. This marks the deliberate point where work was published upstream.
The Commits within the push are then placed on the timeline using their original Git timestamps. If a developer commits locally throughout the day and pushes once at the end, WorkSights shows the actual chronology of their work rather than a single end-of-day spike.
WorkSights displays the commit message as the activity title.
Time Tracking from Commit Messages
If a commit message includes a hashtag-style duration value (for example: #45m, #2h, or #1h30m), WorkSights reads this and associates that duration with the commit. This gives engineering teams passive time attribution without requiring manual logging. If no duration is included, WorkSights records the commit as activity without a duration.
Data Notes
Commits appear only for mapped GitHub users. If a GitHub username is not mapped to a WorkSights profile, commits from that user will not appear. Commits created before the integration was installed appear only if they are included in a post-connection push.
Troubleshooting
If commit activity is not appearing as expected:
- Confirm the affected user is mapped to their GitHub username in the Users tab.
- If a push appears but individual commits do not, confirm the commits exist in the connected repository and were included in the push.
- Commits from before the integration was installed will not appear unless they are included in a new push.
- For persistent issues, contact support via the in-app chat.