CONTENT CREATION

Weekly Multi-Repo Changelog Rollup

Every Friday, this gathers PRs merged across several repos during the week, writes one unified human-toned changelog, and deploys it as the latest entry on your microsite.

CategoryContent Creation
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule (Friday)
  • ActionCollect 7-day merged PRs across reposGitHubGitHub
  • LogicSkip if no user-facing merges this week
  • ActionConsolidate into one weekly entryOpenAI
  • ActionCommit dated weekly entryGitHubGitHub
  • OutputRedeploy microsite on VercelVercelVercel

What it does

Produces a single weekly changelog spanning multiple repositories. Instead of tying entries to tags, it works on a cadence: each Friday it sweeps the past seven days of merged PRs across every repo you list, merges them into one narrative grouped by product area, and publishes a dated weekly entry.

When to use it

Use it when you ship continuously across several services and tags do not map cleanly to customer-visible releases, but you still want a predictable weekly update on your changelog site.

How it works

  1. 1A scheduled trigger fires every Friday afternoon.
  2. 2The flow queries each configured repo for PRs merged in the last seven days.
  3. 3If the week had no user-facing merges, it skips publishing entirely.
  4. 4An LLM step consolidates everything into one weekly entry grouped by product area, deduping cross-repo work.
  5. 5The entry is committed with this week's date as the slug.
  6. 6Vercel redeploys the microsite with the new weekly entry on top.

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 VercelDeploys, runtime logs, analytics.
  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.