Linear supports linking your issues to GitHub and automates your pull request workflows.
The GitHub and GitLab integrations move issues from In Progress to Done automatically so you never have to update issues manually. It takes less than a minute to connect GitHub to the workspace and then go to team settings to configure the automatic updates.
Link Linear issues to GitHub pull requests. Automate your PR workflow so that issues update when PRs are drafted, opened, merged, and when reviews are requested. You can link single or multiple issues to a specific PR. The integration also autolinks Linear issue IDs in GitHub conversations. If you're having issues with the integration, see debugging suggestions for common problems in the FAQ.
Cmd/Ctrl Shift . to copy git branch name
G then S to go to Settings to set up integration and Team settings to set up PR workflow automation
- Right-click over the issue to copy git branch name from lists or boards or use the sidebar button from issue view
- Click the Avatar to go to Settings to set up integration and Team settings to set up PR workflow automation
git to copy git branch name
settings to go to Settings to set up integration and Team settings to set up PR workflow automation
Go to Settings to enable the GitHub integration. The GitHub integration doesn't require much beyond authenticating to GitHub and choosing what statuses to apply when PRs are created, request review, and merged
To enable GitHub, click Connect GitHub in integration settings and select which repositories you want to give Linear access to. It's easy to add or remove repositories later; just visit settings through the Configure GitHub button from Linear's Github integration settings page. All teams in your workspace will be able to link to issues in the selected repositories.
If you're using GitHub Enterprise Cloud and have IP Allow List security setting enabled, you'll also need to turn on Enable IP allow list configuration for installed GitHub Apps setting to enable Linear's GitHub integration. Read more here. Linear doesn't currently support GitHub Enterprise Server but we're consider adding support for it.
If you want to automatically resolve your Linear issue IDs (e.g. ENG-123) in PR descriptions or comment to links, you can enable this using GitHub's Autolink references feature. See instructions on GitHub.
Use the following URL format:
workspace corresponds to your workspace's URL and
ID is the issue identifier key for your team. You need to add each team separately as they all have a different ID pattern.
Once you connect Linear with GitHub, you can start linking your GitHub pull requests to Linear issues.
You can link PRs to issues three ways: by including the
issue ID in the branch name, adding the
issue ID in the PR title, or prefacing an
issue ID with a magic word in the PR description (e.g.
*issue ID* in the branch name to link the issue to a Pull/Merge Request.
The fastest way to link to issues is to use Linear's branch name feature. Set the branch format in the integration settings, then use the Copy git branch name action or shortcutCmd/Ctrl Shift . when viewing or selecting an issue. It will give you a uniform branch name with the issue ID which you can use to start working on your feature or bug.
We recommend using common branch naming patterns throughout your teams.
- Good branch names are descriptive and helpful as you browse through commits.
- Linear's default branch name consists of your username, issue ID and the issue title which incorporates the most essential information about the issue (e.g.
- If your team prefers another pattern, you can always change it in the integration settings.
Pull/merge request title
Include the Linear issue ID (e.g. ID-123) in the title when creating pull requests on GitHub or merge requests on GitLab.
To link multiple issues to a single pull request, or to link to a pull request after creating it, you can use the magic word linking method by including multiple closing statements in the description (e.g.
Fixes ENG-123, DES-5 and ENG-256). Linking will happen after you save your changes.
Magic words must be used in the description. The integration cannot link via comments or commit messages.
You can use the following magic words to link issues: close, closes, closed, closing fix, fixes, fixed, fixing resolve, resolves, resolved, resolving complete, completes, completed, completing
Set up pull request automation so that updates to PRs change the status of linked Linear issues. This saves you the hassle of updating Linear issues manually.
Customize the PR automation in team settings under Workflow. By default, we'll move linked issues to In Progress when PRs are open and Done when PRs are merged. You can configure status updates when PRs are drafted and request review. Since this is a team setting, it must be configured for each team in your workspace.
When an issue is linked with a pull request, Linear posts a linkback message as a comment with the issue title and description. All the pull requests are also listed in the issue details in Linear. This makes it faster to reference without jumping between apps. You can disable linkbacks in private or public repositories in the integration settings.
Link multiple PRs
You can link multiple Linear issues to a single PRs by using magic words. You can link multiple PRs to a single Linear issue using any linking technique. We won't close the Linear issue until all PRs have been closed.
Auto-assign and update status
Save yourself a few steps by toggling on our automations that auto-assigns the issue to you and move it to a started status when you copy the git branch name. The issue moves to the first started status in your team's workflow, which you can customize under team settings > workflow.
Our Git integrations speed up communication between developers and the rest of your team. Anyone subscribed to an issue will get a notification that it's been completed immediately upon PR merge (this includes creators of the issue, who are subscribed by default).
If you set up the Slack integration for team or project notifications, it'll send an update to the selected channel. If you've connected one of our customer support integrations, conversations with affected users will be re-opened automatically upon PR merge so that you can let them know a feature shipped or bug was fixed.