Engineering

Sync GitHub issues to Linear tickets

When someone opens a GitHub issue, Carly creates the matching Linear ticket, copies the description, and assigns it to the right team — keeping engineering's source of truth tidy without manual triage.

The prompt
When a new issue is opened in our GitHub repo, create a matching Linear ticket in the Engineering team with the same title and description. Add the GitHub issue link in the Linear ticket. Auto-assign based on which area of the repo the issue mentions.

What Carly will set up

  1. 1
    GitHub GitHub New issue opened
  2. 2
    Detect which area or component the issue is about
  3. 3
    Linear Linear Create ticket in the Engineering team with title, description, and GitHub link
  4. 4
    Linear Linear Auto-assign based on area

Apps used

GitHub GitHub
Linear Linear

Frequently asked

Can I filter to only certain repos or labels?
Yes. Add 'only issues in the carly-app repo' or 'only issues with the bug label' to the prompt. Carly will skip issues that don't match.
What about issue updates and comments?
By default, only the creation event triggers the sync. If you want bidirectional sync — comments, status changes, assignees — tell Carly and she'll keep them in lock-step.
Can Linear tickets sync back to GitHub?
Yes — flip the prompt: 'when a Linear ticket is created in Engineering, open a GitHub issue in the relevant repo'. You can run both directions if needed.
Does this work with Jira or Asana?
Yes. Replace Linear with Jira, Asana, ClickUp, or any project tool. The sync logic is identical.

Ready to build this with Carly?

Copy the prompt above, send it to Carly, and she'll set up the workflow for you.

Build this with Carly →