Last updated
April 29th, 2026

GitHub Pull Requests

Pull requests are central to code review and collaboration in GitHub. WorkSights ingests PR metadata to give teams visibility into when developers propose changes, review work, and update branches, without accessing any source code.

For connection steps, see GitHub Setup.

What WorkSights Receives

WorkSights receives PR events through the GitHub App webhook framework:

  • 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)
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

Each PR event appears as a structured timeline entry:

PR Opened: marks the creation of a new pull request, showing 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. This appears as a PR update event. The individual commits appear separately in the Commits guide.

PR Closed or Merged: displays a closure event indicating whether the request was merged or closed without merging.

PR Comments: appear as standalone events tied to the PR. WorkSights shows author, timestamp, and link context only. Comment text is never shown.

If a developer participates in a PR through comments or updates, that participation appears as activity on their timeline.

Data Notes

PR activity appears only for mapped GitHub users and only from repositories where the WorkSights GitHub App is installed. Activity created before the integration was installed will not appear. WorkSights represents each PR event at the timestamp GitHub provides.

Troubleshooting

If pull request activity is not appearing as expected:

  • Confirm the affected user is mapped to their GitHub username in the Users tab.
  • Check that the repository is included in the GitHub App installation scope.
  • PR activity from before the integration was installed will not appear.
  • For persistent issues, contact support via the in-app chat.

Related Guides

GitHub Overview

GitHub Setup

Commits

Comments