Last updated
November 12th, 2026

GitHub Setup

WorkSights connects to GitHub through a GitHub App installation with read-only permissions. Once installed, GitHub delivers activity events to WorkSights for the repositories you grant.

Only Owners, Executives and Admins can connect services.

For an overview of how GitHub activity appears in WorkSights, see GitHub Integration Overview.

Connecting GitHub

Step 1: Start the Connection

  1. Go to Services in the top navigation
  2. Find GitHub in the list
  3. Click Connect GitHub
GitHub card on the WorkSights Connected Services page

Step 2: Install the WorkSights App in GitHub

GitHub opens its App installation screen. The installer must be a GitHub organization owner or admin. Members can start an install if the organization allows it, pending approval. Personal accounts also work, though member import is skipped for them.

Choose All repositories or Only select repositories. Activity flows only for granted repositories. You can adjust the repository grant later from GitHub's own settings.

The App's permissions are read-only. WorkSights cannot modify anything in your GitHub organization.

Step 3: User Mapping

GitHub identifies people by GitHub username, not by email.

Users tab of the GitHub service in WorkSights showing remote user mapping

After installation you land on the Users tab. This is the critical step.

GitHub identifies people by username and keeps member emails private, so automatic matching by email is best-effort and most mappings need to be done by hand. Map each GitHub username to the correct WorkSights user. Pay particular attention to contractors and external contributors, who may use unfamiliar handles.

Unmapped users generate no activity, and events that arrive before mapping are not replayed. Up to 500 organization members are imported at install time, with a daily re-sync after that.

What Happens Next

Once installed and users are mapped, activity appears within about 20 minutes of commits, pull requests and comments happening in the granted repositories. Historical activity is not backfilled.

Overview tab of the GitHub service in WorkSights

Developers can add #time tags to commit messages, for example "#time 1h 30m", to set explicit durations on their commit activity. Without a tag, Code activities use a 10-minute default.

Repository grants are managed from GitHub's Settings → GitHub Apps page. You can review and update user mappings at any time from the integration page.

Related Guides

GitHub Overview

Commits

Pull Requests

Comments