Sync multiple teams/repos

[zomars]

Can we sync the whole organization instead of individual repos? That way we can use Linear as a "central command" for our mix of public and private repos.

[tedspare]

Thanks for raising this @zomars. Many-to-many sync is desirable (see #10), agreed. In that case, which Linear team would receive the ticket broadcast by a GH repo?

[janbaykara]

I would reframe this feature request as "connect a team to a github org". Our use case is that we want to sync many repos to one linear team.

Ideally, we'd have a way of determining which Public linear issues sync to which repo, likely by matching a Linear team + project to a Github repo.

[PeerRich]

@janbaykara that needs a bit of architecture discussion as this can quickly creep out of scope

[janbaykara]

Agreed. I'm not familiar with the architecture at present. Is there any kind of diagramming / documentation already, or would it just be a case of looking through the code, if I wanted to contribute to that discussion?

[tedspare]

@janbaykara I'll share some diagrams and documentation soon™️. They're scattered currently.

One approach would be to replace the single Public label with a label for each repo: commonknowledge/a, commonknowledge/b, etc. Would that fit more closely with your expectations?

[janbaykara]

Yep, a per-repo label would make sense!

[IronSean]

I was about to open a new issue when I noticed that this issue also could cover my use case. Here was going to be my proposal:

---

Is there any way to sync one Linear team to different repos?

Use Case
We are a single team that does work on multiple projects that are in multiple repos (in multiple orgs). We have one linear team because our team has one velocity which might prioritize one project over the other in a given cycle. That means we can't just have different teams per project as the velocity will not be consistent. We use projects to track the different projects in our linear team, and each project has a separate repo and relevant public issues. If we could control which issues go to which repo that would allow us to set up sync for more than one project in the same team.

Possible solutions

1. Configuration where a linear project is mapped to a github repo, so Public issues on that project get synced to that repo.
2. Separate Linear tags for each repo, so we could customize ProjectA to become public on repo A.

[nikitnikoks]

It'd be great to have this feature. We also use multiple repos for one team, so we are unable to use the integration at this point.

[marcklingen]

Same issue for us; multiple repos (application, sdks, docs) and one team

[mohab-sameh]

Same issue here. Came by your issue by coincidence @zomars. Wonder if you found a workaround or if using a monorepo at Cal.com doesn't make a critical issue?

[galligan]

Would also support repo-based issue labeling. In dealing with multiple repos, but the same team working on them, this would be a huge improvement.

[bmhtech07]

My team could really use this. Small team working across multiple projects in multiple repos (separate tags for each connected repo would be ideal!)

Is there a timeline for this? Would probably be able to find some time to contribute, but couldn't lead the project.

[janbaykara]

I wonder if this is a bit of work and we can usefully try to map out what needs to happen to make this possible?

It looks like a lot of the logic is in https://github.com/calcom/synclinear.com/utils/webhook/github.handler.ts - could someone make some notes in this issue so we can try and scope it out a bit and maybe someone could even use that info to submit some PRs.