🎉 Linear now supports GitHub sync natively 🎉

[tedspare]

[!TIP] Linear now supports native two-way sync of tickets and GitHub issues 🎉

The following properties will sync:

• description
• status
• comments (in a synced thread)
• labels
• assignee

Unless you use Milestone <> Cycle/Project sync, this new offering should cover your use case.

To set it up, go to Settings > Integrations > GitHub > Connected organizations > +:

I encourage all to try it and provide feedback to Linear, or here if preferred! Linear is a VC-backed, profitable business with clear product acumen.

Note: I'm a third-party, informal maintainer of this project; my words don't represent Cal.com in any capacity.

cc: @jorilallo

[nickzelei]

The native integration seems to be pretty limited in scope. While it does work quite well, it seems to only handle issues that come from Github. It doesn't handle issues that are created in Linear. This is pretty limiting. Coincidentally, Synclinear doesn't seem to handle issues coming from Github. So both integrations are kind of solving the opposite side of the vendiagram when sourcing issues.

Maybe synclinear works when creating in Github if you've connected, but we had some community members create issues in Github and they don't sync with Linear, even after adding the linear tag to them.

Also as of today, the native integration has no way of filtering tags. So overall their integration seems pretty limiting, but hopefully it gets better over time.

[quinn-linear]

@nickzelei issues created in linear can now be synced to github as of today. It's a setting toggle in the Linear settings > Integrations > Github and in the edit menu for the repo that's connected

[nickzelei]

cool, thanks for letting me know - Ill check it out!

[hongsw-aibizon]

https://linearcustomers.slack.com/archives/C01BBH68ZN1/p1709675224857309 Many people here find the default integration inconvenient. Instead of a default repository per team, a project-specific default repository connection is needed. @nickzelei Thanks