Table of contents
Pull requests (PRs) are central to code review and collaboration in GitHub. WorkSights ingests PR-related metadata to give teams clear visibility into when developers propose changes, review work, or update a branch – all without accessing any source code.
WorkSights processes PR activity in near real time, helping teams understand collaboration patterns, review cycles, and decision points across the engineering workflow.
What WorkSights Receives
WorkSights receives PR-related events directly from the GitHub App webhook framework. These include:
- PR opened
- PR edited (title or description changes)
- PR synchronized (new commits pushed to the PR branch)
- PR closed (with or without merge)
- Comments on the PR (issue-style comments, not code diffs)
Note: GitHub treats pull requests and issues as related objects. PRs appear as issue-like events with additional pull request metadata.
WorkSights does not ingest diff data, changed lines, or repository content.
How Pull Requests Appear in WorkSights
Pull requests activities appear as structured events with clear context:
PR Opened
Marks the creation of a new pull request. WorkSights displays the PR title and repository.
PR Edited
Shows updates to the PR title or description, providing visibility into iteration and clarification.
PR Synchronized
Triggered when new commits are pushed to the PR branch. WorkSights shows this as a PR update event – not individual commits (commits appear separately in the Commits guide).
PR Closed or Merged
Displays a closure event, indicating whether the request was merged or simply closed by the developer.
PR Comments
Comments appear as standalone comment events tied to the PR. WorkSights shows only metadata (author, timestamp, link context), never the comment text.
Together, these events give an accurate timeline of collaboration without exposing code.
Code Review Visibility
If a developer participates in a PR through comments or updates, that participation appears as activity on their timeline.
WorkSights does not ingest:
- Review body text
- Approval/request-changes content
- Diff-based comments
Instead, review interactions appear as metadata-only comment or PR-update events, providing visibility without surfacing sensitive technical discussion.
Data Details and Requirements
Only mapped GitHub users generate PR activity in WorkSights.
WorkSights receives PR activity only from repositories where the WorkSights GitHub App is installed.
PR activity created before the integration was installed will not appear.
WorkSights does not ingest branch content, code diffs, or review details.
WorkSights represents each PR event at the timestamp GitHub provides.
Next Steps
For commit-level changes included in pull requests, see GitHub Commits.
For review comments and collaboration activity, see GitHub Comments.
For configuration steps and permissions, see GitHub Setup.
For a platform-level explanation of GitHub activity, see GitHub Overview.