In Linear, go to Settings, Features, Integrations, GitHub, click Enable, choose your GitHub organisation and repositories, click Install and authenticate your personal account. Then link pull requests to issues with branch names, PR titles or magic words such as Fixes ENG-123. Zapier is the connector route for custom actions.
Installing the GitHub app from Linear
- In Linear, go to Settings > Features > Integrations > GitHub and click Enable.
- Select the GitHub organisation and choose All repositories or Only select repositories, then click Install.
- Authenticate into your personal GitHub account.
- Ask each teammate to connect their own GitHub account under Settings > Connected accounts.
- Set issue status automation so linked pull requests and merges move issues through your workflow.
Step four's easy to skip, and it's worth chasing. Without it, activity, synced comments and assignees show up as generic GitHub activity instead of being tied to the right person.
If your GitHub organisation uses an IP allow list, you'll need to enable the setting for installed GitHub Apps or allow Linear's IP addresses, or the connection won't work, and you'll get no clear error telling you why.
Three ways to link a pull request
- Branch name: put the issue ID in the branch name. Copy it from Linear with Cmd/Ctrl + Shift + .
- PR title: include the issue ID in the title.
- Magic word: write a magic word plus the issue ID in the description, such as Fixes ENG-123.
Adding {TEAM}-NEW, for example ENG-NEW, to a pull request description creates a new issue in that team and links it, which is handy when the fix came before the ticket. It's a small thing, but it'll save you a context switch.
Magic words cheat sheet
| Type | Words | Effect |
|---|---|---|
| Closing | close, fix, resolve, complete, implement (and their variants) | Links and moves the issue on when merged |
| Non-closing | ref, refs, part of, contributes to | Links without closing |
| Relation | relates to, related to | Marks the issue as related |
| Opt-out | skip or ignore with the ID, such as Ignore ENG-123 | Stops automatic linking |
Tying commits to issues too
Commit linking is separate. Turn on Link commits to issues with magic words, then add a webhook in GitHub using the Payload URL and Secret from Linear, with the application/json content type and Push events. It works with a single GitHub organisation only.
Syncing GitHub Issues both ways
If your team also uses GitHub Issues, you can sync them one-way (GitHub to Linear) or two-way. Several repos can feed one Linear team one-way, but only one repo can be two-way at a time. Synced properties include title, description, status, assignee, labels, sub-issues, comments in the synced thread and priority. Only newly created issues sync, so existing GitHub issues have to be imported.
One organisation, one workspace
Linear Docs flag the structural limit. One GitHub organisation can only be connected to one Linear workspace, because a GitHub App installs once per organisation. Multiple GitHub organisations are supported for pull request automation only, and commit linking only works for a single organisation. If you run separate Linear workspaces for different clients, plan your GitHub organisations around that.
Linear also notes that some features depend on plan, such as AI issue writing on Business and Enterprise, and GitHub Enterprise support on Enterprise.
Connector routes for custom jobs
Zapier offers Linear and GitHub templates, such as creating Linear issues from new GitHub issues, and creating GitHub issues for new Linear issues. Use it for jobs the native integration doesn't cover, and don't run both for the same action or you'll get duplicates.
Jira teams can do similar things through Zapier, which lists Jira Software Cloud and GitHub templates such as creating GitHub issues from new Jira issues.
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.
If you're reviewing your tools, my roundups of other issue trackers and code hosting options cover the field.
The advice I'd give an engineering lead
Install it, then make every developer connect their own GitHub account the same day. Agree on one linking habit, ideally the issue ID in the branch name, and teach the closing words so merges move issues without anyone touching Linear. Add commit linking only if you need it. And if you're using AI to speed up the code itself, my Copilot prompt guide is worth a look.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.
Frequently asked questions
Do I need Zapier to connect Linear and GitHub?
No. Linear has a native GitHub integration, and Zapier is only for custom automations.
How do I link a pull request to a Linear issue?
Include the issue ID in the branch name or PR title, or use a magic word such as Fixes ENG-123.
Does it sync GitHub Issues?
Yes, one-way or two-way, for newly created issues. Existing ones have to be imported.
Can I connect two GitHub organisations?
Yes for pull request automation, but commit linking works with a single organisation.
Can two Linear workspaces use one GitHub organisation?
No. Only one Linear workspace can connect to a GitHub organisation.
