Sync milestones <> cycles

[tedspare]

Summary

• 1:1 sync of Linear cycles and GitHub milestones

Test Plan

• Create Linear cycle in synced team. Ensure milestone is created with same title, description, open state (unless past endsAt), and link in footer.
• Edit Linear cycle title, description, and state. Ensure milestone is synced.
• Create GH milestone in synced repo. Ensure Linear cycle is created with same title, description, and end date.
• Edit milestone title and description. Ensure cycle reflects changes.
• Mark milestone as completed. Ensure cycle endsAt date is set to today.

TODO:

• Auto-update webhooks to include milestone/project events
• Synced ticket added to synced cycle <> synced milestone assigned to synced issue

Related Issues

Closes #5

[PeerRich]

lets goo

[scopsy]

A small question here, why not syncing linear milestones to linear milestone?

I know this is maybe how we work, but we have milestones for version releases that work as follow:
For example a v0.9.0 milestone is a milestone on both Linear and GitHub, we then have multiple projects associated to each milestones.

GitHub doesn't really have a similar of "Epics" or "Projects" Today we just create another Issue for those marked as "Tracking" or "Epic".

Syncing projects to milestones won't work for us, so having a way to disable it would be great

[scopsy]

Sorry, they are called Roadmaps in Linear now (they renamed it recently)

[tedspare]

Hey @scopsy - valid concern, @PeerRich and I have been looking for a solution.

How hard would it be for your team to switch to using Linear Projects for releases? What about mapping Cycles <> Milestones?

[scopsy]

Hi @tedspare seems like you need to enable roadmaps in settings.
Projects are not quite feasible for us since we usually have a few big projects running, and we organize them with owners and etc...

Cycles might work for us, but only because we work in the shapeup method with quite a large cycle. I believe most teams working in classical sprints.

[PeerRich]

lets merge this for "cycles" and we can later add a dropdown select where github milestones should sync to

[scopsy]

Sounds good, but would be great if this could be somehow disabled even with an env variable, because it will auto sync for us things in a not expected way 🙏

[PeerRich]

whats missing for this to go live?

[tedspare]

Hey @scopsy would you be open to reviewing this? It's opt-in to sync cycles <> milestones.

[scopsy]

Looks fantastic @tedspare!

[PeerRich]

@scopsy can you review the code and approve?

[tedspare]

Re-reviewed:

• Removed some unused code
• Prevented an infinite loop of milestone/cycle assignment