SUMMARIZATION

Milestone wrap-up: summarize a closed GitHub milestone into a stakeholder email

When a GitHub milestone is closed, this gathers all its merged PRs and resolved issues, distills them into an executive summary with metrics.

CategorySummarization
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerGitHub milestone closedGitHubGitHub
  • ActionFetch milestone PRs and closed issuesGitHubGitHub
  • LogicCompute delivered, count, and carryover metrics
  • ActionWrite executive milestone summaryOpenAI
  • OutputEmail wrap-up report to stakeholdersGmailGmail

What it does

Produces an executive milestone report the moment a milestone closes. It pulls everything that landed under that milestone — merged PRs and closed issues — and writes a concise wrap-up covering what was delivered, headline metrics, and anything that slipped, then sends it as a clean email.

When to use it

For teams that organize work into GitHub milestones and owe stakeholders a delivery summary at the end of each one. Removes the manual end-of-milestone report writing.

How it works

  1. 1A GitHub milestone-closed event triggers the workflow.
  2. 2The flow fetches all merged PRs and closed issues tagged to that milestone.
  3. 3A logic step computes simple metrics: items shipped, PR count, and any still-open carryover.
  4. 4An OpenAI step writes an executive summary with a 'Delivered', 'Metrics', and 'Carried over' structure.
  5. 5The formatted report is emailed to the stakeholder list through Gmail.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitHubRepos, issues, pull requests, actions.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect GmailRead, draft, send, label.
  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.