GitHub

1. An Admin or Owner installs the WePeople GitHub App on your GitHub organization from Organization → Integrations.
2. Choose which repositories to include during install (you can add more later in GitHub settings).
3. Link each monitored worker to their GitHub username under People. Unmapped commits and PR events are excluded.

Marketing walkthrough with FAQs: GitHub integration page.

On roughly an hourly sync, WePeople ingests commit metadata: timestamp, author, repository name, and lines added / deleted counts. Events appear on the timeline as github_commit and overlay alongside Slack presence for the same org-local day.

Line counts are a volume signal for rhythm and capacity — not a quality or impact score.

Pull-request lifecycle events — opened, reviewed, merged, closed — land as typed timeline events such as github_pr_opened, github_pr_reviewed, and github_pr_merged. Cycle time from open to merge and review participation roll up into reports.

Review events (requested, submitted, approved, changes requested) are tracked. Comment text is not ingested.

Scope the GitHub App installation to repositories that matter for monitoring. Repositories outside the installation are invisible to WePeople — useful for excluding experiments, forks, or archived codebases.

• Monorepos with many inactive packages — include only active service repos.
• Open-source mirrors or vendor forks that do not reflect team delivery.
• Personal sandboxes under the org — exclude unless intentionally monitored.

GitHub App permissions expose metadata only. WePeople does not pull or store:

• Source code files or diff bodies
• Full commit message bodies
• Code review comment content
• Repository secrets, Actions logs, or configuration files

See also trust model and the read / do-not-read matrix.