When a release is published
Comment on Linear issues a release ships
When a GitHub release is published, Leta finds the Linear issues in it and comments on each with the version and release link.
Linear + GitHub integration
Combine Linear + GitHub and move repo activity into Linear. Just ask Letaido's AI agent and watch it do the work.
Best Linear and GitHub integration jobs to start with
Use this Linear GitHub integration to note releases on shipped issues, check launches, file marketing tasks and list customers to tell.
Every Thursday at 10am
Weekly launch check against GitHub
Every Thursday, Leta matches open issues in your Linear launch project to GitHub pull requests and comments on the latest project update with what's at risk.
When a feature PR merges
Marketing task when a feature merges
When a pull request labeled customer-facing merges into main, Leta files a Linear task for marketing with a plain-English summary and the PR linked.
When a release is published
Customers to tell after each release
When a GitHub release is published, Leta finds the Linear customer requests behind the shipped issues and files one issue listing who to tell.
Linear GitHub integration options, compared
Linear's own GitHub integration links pull requests to issues and moves their status. Letaido covers the jobs after the merge.
| Option | Links pull requests to issues | Notes the release on shipped issues | Customers to tell after a release | Launch risk check | Plain-English notes for marketing |
|---|---|---|---|---|---|
 Letaido AI agent | Partly | Yes | Yes | Yes | Yes |
| Linear for GitHub | Yes | Partly | No | Partly | No |
| Linear Agent and Loops | No | Partly | Partly | Partly | Yes |
| Zapier | Partly | Partly | No | No | Partly |
Read the full comparison
| Option | Direction | What starts it | Best for | Watch out for |
|---|---|---|---|---|
| Letaido AI agent | GitHub into Linear: releases, merged pull requests and pull request status land on Linear issues and projects | A GitHub release or merged pull request, a schedule, or when you ask | Jobs for the people around engineering: shipped issues get the release, a weekly launch check, marketing tasks for customer-facing merges, customers to tell after a release | Not a replacement for Linear's pull request linking or status automation. It finds issues by their ID in commits and pull requests. GitHub event jobs need a token with the Webhooks permission |
| Linear for GitHub | Both ways: pull requests and commits linked to Linear issues, plus optional GitHub Issues sync | An issue ID in a branch name or pull request title, or a magic word like Fixes ENG-123 | Developers: issue status follows pull request activity, review state shows on the issue, pull requests can be reviewed in Linear | A Linear owner or admin sets it up. A GitHub repository admin can install it for repository access; organization access needs a GitHub organization owner. Two way issue sync works with one repo at a time and only for new issues. Release tracking is a separate Releases setup in your CI, on Business and Enterprise plans |
| Linear Agent and Loops | Inside Linear, reading connected GitHub repos | A schedule, Linear events including a pull request merging, a Slack message, or a webhook | AI work in Linear, such as user-facing messaging after an issue closes or weekly summaries of a team's work | Loops use AI credits and pause when they run out. An admin must allow loops to access code. Code Intelligence needs the Business or Enterprise plan |
| Zapier | GitHub into Linear, or Linear into GitHub, one recipe at a time | A GitHub trigger checked on a polling interval, or a Linear event | Fixed recipes such as a Linear issue for each new GitHub pull request, or a Linear comment for each new commit | GitHub triggers poll: Zapier checks for new data every 15 minutes on its lowest plan. Writing summaries needs an AI step you add and set up in the Zap |
Linear and GitHub: the old way vs. Letaido
- 1Open the new release
- 2Read the commits since the last one
- 3Find each Linear issue
- 4Comment with the version
- 5Paste the release link
When a release is published on acme/app, compare it with the previous release and pick out the Linear issue IDs (like ENG-412) in the commit messages. Comment on each of those Linear issues: 'Shipped in <version> on <date>' with the release link. Skip IDs that aren't Linear issues.
acme, tab Issues commented on
ENG-412, Shared dashboards with a read-only link, Shipped in v4.3.0
ENG-418, CSV export keeps your filters, Shipped in v4.3.0
How Linear and GitHub jobs start
When something happens
A job can start when a GitHub release is published or a pull request is merged in GitHub, like “Comment on Linear issues a release ships”.
On a schedule
Saved as an automation, like “Weekly launch check against GitHub”: every Thursday at 10am.
When you ask
Ask in chat; Leta picks from 77 actions.
How to set up the Linear GitHub integration
-
1Paste a Linear API key
-
2Install the GitHub App or paste a token
-
3Approve the first run in chat
Allow all read operations once per app; approve each kind of write once.
-
4Try it in chat first
-
5Choose when it runs
Every Linear and GitHub action the agent can take
Linear
9 groups: 18 reads, 9 writes
- Find and list issues
- Manage issue labels and attachments
- Manage projects
- 6 more
Get viewer · Create customer need · Create comment · Remove label from issue
GitHub
13 groups: 31 reads, 19 writes
- Read issues and search
- Create and update issues
- Monitor GitHub Actions workflows
- 10 more
Submit review · List issue comments · Delete file · Create branch
Frequently asked
Does Linear integrate with GitHub? +
Yes. Linear's own GitHub integration links pull requests to issues and moves their status. Letaido covers the jobs after the merge: its AI agent, Leta, can use Linear and GitHub in the same job, like commenting on each Linear issue a release ships.
How do I connect Linear and GitHub to Letaido? +
Paste a Linear API key, then install the GitHub App or paste a GitHub token. Then describe the job in chat, or paste a prompt from a job on this page.
Can a merged pull request start a job in Linear? +
Yes. A GitHub release being published or a pull request being merged can start a job, or it runs on a schedule you set, or when you ask. GitHub event jobs need a token with the Webhooks permission.
Is it a two way sync between GitHub issues and Linear? +
No. Letaido is not a two way sync. Linear's own GitHub Issues sync does that, for new issues, with two way sync on one repo at a time. Letaido runs jobs that read GitHub and write to Linear.
Which Linear issues count as shipped in a GitHub release? +
Leta reads the commits between the new release and the previous one and picks out Linear issue IDs like ENG-412, including merge commits that carry the branch name. A change with no issue ID isn't found.
How is Letaido different from Linear's GitHub integration? +
Linear's integration is for developers: it links pull requests and commits to issues and moves issue status. Linear Agent and Loops can add AI work in Linear, but use AI credits. Letaido runs jobs for the people around engineering, like a weekly launch check or a list of customers to tell after a release.
Will it ask before it changes Linear? +
Yes. Allow all read operations once per app; approve each kind of write once. The jobs on this page only read GitHub.
Put Linear and GitHub to work today
Connect Linear and GitHub, then ask for a job like "Comment on the Linear issues each GitHub release ships". Leta gets it done the moment something happens, or the moment you ask.
Get Letaido