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
Each commit in a push becomes its own activity, titled GitHub Commit and Push. The activity detail includes the full commit message and lists of added, modified, and removed files. Code diffs, changed lines, and file contents are never received.
Merge commits are skipped by design. The work in a merge is already recorded on the branch's individual commits, so ingesting the merge would double-count it.
Commits from bots, including Dependabot and CI tooling, are filtered and never appear.
Duration Tags
Code activities default to 10 minutes. To record an explicit duration, include a #time tag in the commit message, for example "#time 45m" or "#time 1h 30m." WorkSights sets the activity duration from the tag, capped at 10 hours, and back-dates the start time so the activity ends at the commit timestamp. Without a tag, the 10-minute default applies.
Troubleshooting
Commits are not appearing
Confirm the committing user's GitHub username is mapped in the Users tab. Confirm the repository is included in the App's installation grant. Commits from before the integration was installed will not appear.
A specific commit is missing
Check whether it is a merge commit. Merge commits are skipped by design.
All commits show as 10 minutes
This is the default duration. Add #time tags to commit messages for accurate durations.