CONTENT CREATION

Weekly merged-PR roundup published to ReadMe changelog

Every Friday, gathers the week's merged GitHub pull requests, drafts a single dated changelog entry in customer voice, and publishes it to your ReadMe developer hub changelog.

CategoryContent Creation
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule (Friday)
  • ActionCollect PRs merged in the last 7 daysGitHubGitHub
  • LogicKeep only customer-facing labeled PRs
  • ActionDraft one consolidated changelog entryOpenAI
  • OutputPublish dated entry to ReadMe changelogReadMeReadMe

What it does

Runs on a weekly cadence rather than per-release. It collects all pull requests merged in the last seven days, writes one consolidated changelog entry, and pushes it live to your ReadMe changelog so your public developer docs stay current without manual upkeep.

When to use it

Use it when you ship continuously and don't cut formal version tags, but still owe customers a regular public changelog. Ideal for API and developer-tool companies that host docs on ReadMe.

How it works

  1. 1A scheduled trigger fires every Friday afternoon.
  2. 2The flow searches GitHub for pull requests merged into the default branch in the past week.
  3. 3A filter keeps only PRs labeled customer-facing and discards internal refactors.
  4. 4An LLM step composes a single dated entry, grouping items by theme and writing each in plain, benefit-first language.
  5. 5The entry is published to your ReadMe changelog as a new dated post, ready for customers to read.

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 ReadMeAPI docs, changelog, auth.
  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.