Automate GitHub + Linear with GAIA
Sync GitHub PRs and issues with Linear tickets automatically
Linear's own GitHub integration links pull requests, branches and commits to Linear issues and moves issue status for you, with no extra tool. Connect it in Linear under Settings > Integrations > GitHub, then put the issue ID (like ENG-123) in the branch name, PR title or PR description; copying the git branch name from a Linear issue does this for you. In each team's workflow settings, choose the status an issue moves to when you copy its branch name or open a draft PR, when a PR opens or review is requested, and when the PR merges (usually Done). You can add rules per target branch, for example In QA on merge to staging and Done on merge to main. A closing word such as "Fixes ENG-123" in the PR description also closes the issue on merge.
If that covers your team, you do not need GAIA for status updates. GAIA is for the work the native integration does not do: steps that cross more tools or need judgment. GAIA's GitHub triggers fire on pull request events, new issues and pushed commits in the repositories you pick, and its Linear triggers fire when an issue is created or updated or a comment is added in a team you pick. A workflow written in plain English then acts with GAIA's GitHub, Linear, Slack and Gmail tools: post a Slack summary of what merged today, draft release notes from the issues closed this week, or turn alert emails into triaged Linear issues.
An example workflow: "When a pull request is merged in acme/api, find the Linear issue IDs in its branch name and title, comment on each issue with the PR link, and post a one-line summary to #releases in Slack."
5 things you can automate
Everything GAIA can do when GitHub and Linear are connected.
Auto-update Linear issue status from PR events
When a PR is opened referencing a Linear issue, GAIA moves the issue to 'In Review'. When the PR merges, GAIA marks the issue as 'Done'. The Linear board always reflects actual code state.
Create Linear issues from GitHub issues
Bug reports and feature requests filed in GitHub can automatically create corresponding Linear tickets, ensuring engineering backlog and GitHub issue tracker stay in sync.
PR cycle time reporting
GAIA tracks the time from Linear issue creation to GitHub PR merge and generates weekly reports showing cycle time by team member and issue type to identify bottlenecks.
Branch naming convention checks
On a schedule you set, GAIA lists open pull requests in the repositories you choose and flags any whose branch name or title has no Linear issue ID, so untracked work shows up before review.
Release notes generation
When PRs are merged to main, GAIA compiles the linked Linear issues into structured release notes organized by feature area, ready for the changelog or product announcement.
How to set it up
Connect GitHub and Linear to GAIA in three steps.
- 1
Connect GitHub and Linear to GAIA
Authorize GAIA with your GitHub organization and Linear workspace. Select which repositories and Linear teams to synchronize.
- 2
Describe the workflow in plain English
Pick a GitHub trigger (pull request event, new issue or pushed commit) or a Linear trigger (issue created, issue updated or comment added), then write what GAIA should do, for example "when a PR against main references a Linear issue, comment the PR link on the issue". GAIA runs each step with its GitHub and Linear tools.
- 3
Check what ran
Every workflow run is recorded, and GAIA can notify you when it acts. You can also ask GAIA at any time to compare open PRs with Linear issue states and list the mismatches.
Frequently Asked Questions
Explore individual integrations
Compare the tools
Related Automations
Guides in the Docs
Explore more automation combos
GAIA supports dozens of tool combinations. Explore more ways to automate your workflow.
Browse marketplace