Skip to main content
Analyses commits on the project’s tracked GitHub repositories and kicks off a background task that generates a public changelog. Returns immediately with a pending content record.

​
Arguments

​
Returns

Poll get_generation_status until the status is completed, then read the draft with get_content_draft; once published it also appears in list_changelogs / get_changelog and the REST API. A changelog is only produced when the period contains customer-facing product changes. If nothing shipped that customers can use (only marketing-site, docs-hosting, CI, or refactor commits), the run ends failed with skip_reason: "no_customer_facing_changes", no “quiet week” entry is created or published, and the credits are refunded — a scheduled occurrence ends skipped and is not re-drafted. Widen the date range, or pass instructions if that change should have counted.

​
Errors

  • No GitHub account connected — connect GitHub in Sources first.
  • No active tracked repositories — add at least one active repo in Sources.

​
Example prompts

“Generate a changelog covering everything we shipped in the last two weeks.”
“Kick off a changelog for the 2026-03-01 → 2026-03-15 window.”