PROJECT MANAGEMENT

Reschedule the Linear roadmap when a GitHub release milestone slips

Triggers when a GitHub release milestone's due date is pushed back, then shifts the target dates of the Linear roadmap projects tied to that release and posts the revised roadmap…

CategoryProject Management
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerGitHub release milestone date editedGitHubGitHub
  • LogicConfirm slip; compute offset
  • ActionLook up mapped Linear roadmap projectsLinearLinear
  • ActionShift project target dates by the offsetLinearLinear
  • OutputAnnounce revised roadmap in SlackSlack

What it does

This workflow keeps a Linear roadmap honest with engineering reality. When a GitHub milestone that represents a release gets a later due date, it maps that milestone to its Linear roadmap projects and pushes their target dates out by the same slip, then broadcasts the new dates.

When to use it

Use it when releases are planned in GitHub milestones but the customer-facing roadmap lives in Linear projects, and you need the roadmap to move automatically when a release date slips rather than drifting out of sync.

How it works

  1. 1A GitHub webhook fires when a milestone's due date is edited.
  2. 2A logic step confirms the milestone slipped later and computes the offset.
  3. 3The workflow looks up the Linear projects mapped to that release milestone.
  4. 4Each mapped project's target date is moved forward by the offset in Linear.
  5. 5A Slack message announces the release slip and the revised roadmap project dates.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitHubRepos, issues, pull requests, actions.
  2. 2
    Connect LinearIssues, projects, cycles, triage.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.