To connect Notion to GitHub, go to Settings, then Connections, then GitHub in Notion, open Database sync, authorise GitHub and choose your repositories. Pick pull requests, issues or both, choose a history window and select Create sync. Notion creates a read-only synced database, and the sync needs a Business plan.
What the sync does
Notion's managed GitHub sync brings pull requests, issues or both from the repositories you choose into a Notion database. It imports existing records, then checks GitHub for updates in the background. The result is a database you can filter, group and put on a team dashboard next to your specs and roadmaps.
It's one-way. Synced properties are read-only, so any change to a pull request or issue has to be made in GitHub. Think of it as a live window onto your repositories, not a second place to manage them.
Notion's help page says, as of Nov 2026, that this integration replaces the legacy version. Legacy synced databases stay in Notion but stop updating after the cutoff Notion has set, so if your team still relies on an old sync, set up a new one.
Before you start
- Membership of the Notion workspace.
- A GitHub account with access to the repositories.
- A GitHub App installation with access to those repositories.
- A Notion Business plan. Mobile Business also qualifies; other plans aren't supported.
Setting up the sync
- In Notion, go to Settings, then Connections, then GitHub, and open Database sync, connecting your GitHub account if asked.
- Complete GitHub's authorisation and installation steps, then choose the organisation or account. Use Add organization to add another.
- Select the repositories to include.
- Name the sync and choose pull requests, issues or both.
- Choose All history or a window of the last 30, 90 or 365 days, then select Create sync.
- Open the new synced database in your Private sidebar section and build views by repository, state, author or label.
What arrives for each pull request
| Property | Notes |
|---|---|
| Title, PR Number, GitHub URL, Repository | Identify the pull request and link back to it |
| State | Open, Draft, Merged or Closed |
| Author, Labels | Author is a Notion person only when the public email matches a workspace member |
| Base Branch, Head Branch | Where the change is going and where it came from |
| Created, Updated, Closed and Merged dates | Good for cycle-time views |
If the author's public GitHub email doesn't match a workspace member, use the Author (GitHub) property instead, which holds the GitHub username. The pull request Description syncs as plain text rather than rendered Markdown, and the sync doesn't include pull request comments or review details. If your team discusses changes in reviews, that conversation stays in GitHub.
The history window removes pages
This is the part of the Notion Help Center page I'd read twice. History is measured by each record's Updated At time. When a pull request or issue falls outside your chosen window, its Notion page is removed, along with any values in your own Notion properties on it. So if you added a Notes or Priority column and filled it in, those notes disappear once the record ages out of a 30-day window.
If your team annotates synced records, choose All history, or keep annotations in a separate database that links to the synced one.
Managing the sync later
You can pause and resume a sync, add or remove repositories, or change the history window. Removing a repository removes its synced pages. Large repositories, GitHub request limits and temporary outages can delay updates, so a pull request merged a minute ago may take a little while to show as Merged.
Other tools that link code and work
Linear's GitHub integration covers organisation connection, account connection and pull request linking, connecting Linear issues to pull requests through branches, titles or magic words. Linear also documents a Jira integration that connects Jira spaces to Linear teams, for organisations piloting Linear or moving over gradually. If you're weighing up the code side, my roundup of GitHub alternatives covers the field.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
My advice for a product team
Use the sync to give non-developers a clear view of what's shipping, not to manage the work. Pick All history if anyone will add notes to synced pages, build a board view by State, and point people back to GitHub for reviews and comments. If you're new to building views, my guide to how Notion databases work shows how to slice the synced data.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.
Frequently asked questions
Can I edit GitHub data from Notion?
No. Synced properties are read-only, so make changes in GitHub.
Which Notion plan do I need?
A Business plan. Mobile Business also qualifies, and other plans aren't supported.
What can I sync?
Pull requests, issues or both from selected repositories.
Are pull request comments synced?
No. The sync doesn't include pull request comments or review details.
What happens to the old GitHub sync?
Legacy synced databases stay in Notion but stop updating after Notion's cutoff, as of Nov 2026.
