Weekly changelog from GitHub

Q: What is the Keep a Changelog standard?

Keep a Changelog is a popular convention for writing changelogs in a consistent, scannable way. It groups changes under Added, Changed, Deprecated, Removed, Fixed, and Security headings, and recommends semantic versioning. This automation follows the spirit (user-facing changes grouped by type) without forcing strict adherence to the heading names.

Q: How do you automatically generate a changelog from GitHub?

Connect GitHub to Basedash, then schedule an AI automation each week to read merged PRs, filter for user-facing changes, and group them by impact. The output is ready to publish on a /changelog page or email to customers.

Q: Should I include internal changes in my public changelog?

No. The public changelog should only cover user-facing changes. Dependency bumps, refactors, and infra work belong in a separate engineering log that the team can reference but customers don't need to see.

A free changelog template, generated automatically from your merged GitHub PRs every Friday — user-facing changes only, in your voice.

Use this template How automations work

Runs weekly Scheduled Delivered to Email, In-app

Weekly changelog from GitHub

Active

Trigger

Runs weekly

Instructions

Write a user-facing changelog from PRs merged in the past 7 days.

Delivery

Email · In-app

Example output

A realistic sample of what this automation delivers — your version draws on your data.

Weekly changelog from GitHub Runs weekly · Sent to Email, In-app

Sample output

Multi-source automation editor

You can now build an automation that reads from more than one data source in a single run. The editor’s new “Add source” picker lets the AI join across your CRM, billing, and product data in one prompt.

Faster chat retries

Conversations now retry transient model errors automatically, so a brief outage doesn’t break a long analysis. Retries are invisible by default; advanced users can see them in the run log.

Fixes and improvements

Dashboards now respect the workspace’s default time zone in scheduled exports.
Fixed a bug where copying a chart preserved the original’s filter context.
Inviting a user with an existing pending invite now updates the role instead of erroring.

The prompt

Copy, paste, customize.

Drop this into a Basedash automation. AI fills in the numbers from every source you've connected.

Instructions

Write a user-facing changelog from PRs merged in the past 7 days.

Rules:

- Only include user-facing changes. Skip refactors, dependency bumps, internal renames, and infra work unless they materially improve performance or reliability.
- Group large features under their own H3 with a 1-2 paragraph description.
- Collect smaller items under "Fixes and improvements" as bullets.
- Lead with the highest-impact change.

Voice: factual, present tense, no hype words ("amazing", "exciting"). Don't include @mentions of contributors unless explicitly part of a community release note.

Sources: merged GitHub PR titles + descriptions + linked issues. If a PR description is empty, infer the user-facing impact from the diff and PR title.

Data sources