Why Connect GitHub?
Samepage helps Product Managers stay on top of engineering activity without needing to dig through pull requests and commits. By connecting GitHub, Samepage users can:
Build Signals to summarize shipping velocity and PR activity
Spot aging pull requests and CI failures that may block releases
Discover what's been merged, what's in review, and what's stuck
Use the Samepage Copilot to answer questions or draft documents informed by GitHub data
Integration Type
Shared integration — one admin connects GitHub, and the data is available to all users in the workspace.
This integration cannot be configured to limit scope — Samepage imports all repositories the connection has access to.
Data Imported
Samepage imports the following from GitHub:
Pull requests — PR titles, descriptions, status, reviewers, and comments
Commits — Commit messages, authors, and timestamps
CI status — Build and check status for pull requests
Code changes — Diffs and changed files associated with PRs
This data is used to help Product Managers track engineering progress, understand what's shipping, and identify bottlenecks.
Note: We do not import and store GitHub issues.
Sync Behavior
Initial sync pulls pull requests, commits, and CI data from the last 3 months
Ongoing syncs pull changes from the last 1 week, refreshing multiple times per day
How to Connect
You must have an existing Samepage account. If you need one, sign up at samepage.ai.
Go to the Integrations page in Samepage.
Find and click GitHub.
Authenticate your GitHub account and accept the requested permissions.
Samepage will begin importing data from GitHub automatically, refreshing multiple times per day.
What You Can Do After Connecting
Create Signals that analyze GitHub activity — e.g., "Summarize recent commits and pull requests" or "Surface PRs that have been open for more than a week"
Chat with Copilot about GitHub data — e.g., "What shipped this week?" or "Which PRs are blocking the release?"
Combine with other data — Cross-reference GitHub activity with Jira tickets, Slack discussions, or meeting transcripts for a complete picture
Signal Examples Using GitHub
Signal | What It Does |
Shipping Velocity | Summarizes PRs merged this week, who contributed, and what areas of the codebase were affected |
Aging PRs | Surfaces pull requests that have been open without review or are stalled |
CI Failure Tracker | Highlights PRs with failing checks that need attention before merging |
Review Queue | Lists PRs awaiting review and flags those that have been waiting the longest |
Example Signal Prompt
Here's a detailed prompt you can paste into a Signal's instructions field to get a comprehensive engineering activity digest:
Review all GitHub activity from the past week and produce a structured summary focused on shipping velocity:
PRs Merged — List each pull request that was merged, noting the title, author, and a one-line summary of the change. Link to the GitHub PR.
Open PRs Aging — Surface any open pull requests that have been waiting for review for more than 3 days. Note who the assigned reviewers are and whether there are any comments or requested changes.
CI Failures — Identify PRs with failing CI checks. Summarize the failure and note whether it's a flaky test or a real issue.
Ready for Review — List PRs that are marked as ready for review but haven't received any review activity yet.
Key Themes — Identify the top 3-5 areas of the codebase or product features that saw the most activity this week.
Keep it concise. Use bullet points. Include links to GitHub PRs wherever possible so I can jump to the source.
FAQ
Does this integration provide clickable links back to the source? Yes. GitHub pull requests and commits include deep links that take you directly to the PR or commit in GitHub. When Signals or Copilot reference a PR, you can click through to view the full details in GitHub itself.
Privacy
GitHub data is never used to train AI models. Data is processed only to generate Signal outputs and Copilot responses. See Data Handling for more information.