Per-pair page

GitHub + Linear: code in GitHub, tracking in Linear.

Auto-link GitHub PRs to Linear issues, transition issues on merge, and post AI-summarized PR descriptions back to Linear. The default modern engineering pair.

Connect Linear and GitHub See reverse direction

Trigger app

Linear as the trigger

Workflows fire when something happens in Linear.

See all 6 triggers →

Action app

GitHub as the action

Workflows do something in GitHub, instantly.

See all 23 actions →

Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

Linear → GitHub

When something happens in Linear, do it in GitHub.

6 Linear triggers wired to 23 GitHub actions. Most-used pairing: Comment Created → Add Labels.

GitHub → Linear

Or fire it the other way around.

1 GitHub triggers wired to 8 Linear actions downstream.

New GitHub Event

See GitHub → Linear →

Popular pairings

Common Linear → GitHub workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 9 of 138 combinations

When comment created in Linear, add labels in GitHub.

Fires when a comment is added to a Linear issue. Use to mirror engineering discussion to Slack or to feed AI summaries into a status doc.

When comment created in Linear, create comment in GitHub.

Fires when a comment is added to a Linear issue. Use to mirror engineering discussion to Slack or to feed AI summaries into a status doc.

When comment created in Linear, create issue in GitHub.

Fires when a comment is added to a Linear issue. Use to mirror engineering discussion to Slack or to feed AI summaries into a status doc.

When comment created in Linear, create pull request in GitHub.

Fires when a comment is added to a Linear issue. Use to mirror engineering discussion to Slack or to feed AI summaries into a status doc.

When new cycle in Linear, add labels in GitHub.

Fires when a new cycle (sprint) is created in Linear. Use to kick off stand-up bots or to seed a cycle-kickoff doc.

When new cycle in Linear, create comment in GitHub.

Fires when a new cycle (sprint) is created in Linear. Use to kick off stand-up bots or to seed a cycle-kickoff doc.

When new cycle in Linear, create issue in GitHub.

Fires when a new cycle (sprint) is created in Linear. Use to kick off stand-up bots or to seed a cycle-kickoff doc.

When new cycle in Linear, create pull request in GitHub.

Fires when a new cycle (sprint) is created in Linear. Use to kick off stand-up bots or to seed a cycle-kickoff doc.

When new issue in Linear, add labels in GitHub.

Fires when a new issue is created in Linear. The standard inbound hook for routing, enrichment, and SLA-aware notifications.

How it works

Connect Linear and GitHub in five steps.

No code, no glue, no half-day setup. Each step is one click.

1
Connect
Authorize Linear and GitHub
Open Tiny Command, authorize Linear and GitHub once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a Linear trigger
Drop the Linear → Comment Created trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/linear.trigger-comment-created
3
Transform
Add a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
4
Action
Add the GitHub action
Drop the GitHub → Add Labels action below it. Map fields from the Linear payload into the GitHub inputs.
github.add-labels-to-issue
5
Publish
Publish and forget
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about Linear + GitHub.

How does GitHub + Linear sync work?

Linear has first-party GitHub integration that handles much of this. The Tiny Command pair extends it: AI-PR summaries, custom transitions based on labels, multi-issue PR splitting, and more.

How do I auto-move a Linear issue to "In Review" when a GitHub PR opens?

GitHub PR Opened → parse Linear identifier from PR title or branch (e.g., "ENG-123") → Linear Update Issue to state "In Review". Standardizes the engineering flow.

Can I auto-close a Linear issue on GitHub PR merge?

Yes. GitHub PR Merged → Linear Update Issue to state "Done". The Linear native integration does this if the PR mentions the issue (e.g., "Closes ENG-123"); the workflow handles cases where it doesn't.

How do I AI-summarize a GitHub PR into a Linear comment?

GitHub PR Merged → fetch diff → Claude/OpenAI summarize ("explain this change in plain English for a non-engineer") → Linear Create Comment on the linked issue. PMs and stakeholders read the comment, not the code.

Can I assign GitHub reviewers based on Linear team?

Yes. GitHub PR Opened → look up Linear issue by identifier → read the team → assign code review to the matching GitHub team based on a (linear_team → github_team) lookup.

How do I handle PRs that touch multiple Linear issues?

Allow multiple Linear identifiers in the PR title (e.g., "ENG-123, ENG-124"). The workflow parses all of them and fires Update Issue for each. Or split into separate PRs for cleaner tracking.

Other apps that pair well with Linear.

Linear + Gmail

Linear + Slack

Communication

Linear + Google Sheets

Spreadsheets & Databases

Wire Linear to GitHub in 2 minutes.

Free tier available. No credit card. No onboarding call.

Try for free Request a demo

GitHub + Linear: code in GitHub, tracking in Linear.

Pick the way that fits your stack.

When something happens in Linear, do it in GitHub.

Or fire it the other way around.

Common Linear → GitHub workflows.

Connect Linear and GitHub in five steps.

Questions about Linear + GitHub.

Other apps that pair well with Linear.

Wire Linear to GitHub in 2 minutes.

Be the first to know what's next.