Docs, for Moxie Docs
DocumentationGuides
  • Account and email preferences
  • Ask this codebase
  • Changelog from PRs
  • Changelog timeline and overrides
  • Connect repositories via the GitHub App
  • Get started: connect GitHub and reach first doc value
  • Getting started with Moxie Docs
  • Manage email preferences
  • Manage repository conventions
  • Manage subscription
  • Publish knowledge base
  • Review drift cards and open focused doc PRs
  • Search documentation
  • Set up your public knowledgebase
  • Set your collection preferences
  • Tune repository automation settings
  • Use code previews and search helpers
  • Workspace onboarding and invitations
  • Billing, trial, or access issues
  • Configure PR automation and detectors
  • Fix missing or outdated docs in the dashboard
  • Integrate MCP agents with Moxie Docs
  • Integration: connect an MCP-capable agent
  • Opportunity cards seem noisy or wrong
  • Q&A answers seem wrong or outdated
  • Troubleshoot GitHub App and repo access
  • Troubleshoot GitHub App and repository access
  • Troubleshoot GitHub connection and indexing
  • Troubleshoot GitHub PRs
  • Troubleshoot indexing
  • Use the Moxie Docs MCP skill
HomeDocumentationChangelog from PRs

Changelog from PRs

2 min read•Updated Jul 21, 2026

Overview

Changelog from PRs turns your merged GitHub pull requests into a clean, shareable changelog. It automatically summarizes each merged PR, lets you tag entries for different audiences or categories, and gives you controls to edit, hide, copy, or export updates. It’s for anyone who needs to keep teammates and stakeholders up to date without reading every diff.

When to use it

  • Share what changed in your repo after a sprint or release.
  • Create audience-specific updates (e.g., Engineering, Product, Support).
  • Prepare a weekly/monthly update you can paste into chat, email, or docs.
  • Filter out noise and hide internal-only changes before sharing.

How to use it

  1. Open Dashboard → Changelog for your repository.
  2. Select a date range at the top to choose which merged PRs to include.
  3. Review AI‑summarized entries in the list. Each entry shows the PR title, merged date, and a short summary.
  4. Edit an entry by clicking Edit. Update the title or summary to match your voice, then click Save.
  5. Apply tags by clicking Tags on an entry. Choose one or more Audience and Category tags so teammates can filter. Click Done to apply.
  6. Hide noise by clicking Hide on any entry you don’t want in the shared view. Hidden items are excluded from copy and export.
  7. Filter the list using the Filters panel (e.g., Audience, Category, Author, or Status) to refine what will be shared.
  8. Preview the changelog with the Share Preview toggle to see exactly what others will receive.
  9. Copy updates by clicking Copy and choosing a preset (e.g., “All entries,” “Product update,” “Support notes”). The formatted text is placed on your clipboard.
  10. Export by clicking Export and selecting your preferred format (e.g., Markdown, CSV). The export includes only the visible, filtered entries.
  11. Share your copied or exported changelog with your team in your usual channels.

Options and settings

  • Date range: Limits which merged PRs are included in the list and in any copy/export.
  • Filters: Narrow entries by Audience, Category, Author, or Status (e.g., hidden/visible).
  • Edit: Opens a summary editor for the selected entry; changes affect copy/export.
  • Tags: Assign Audience and Category labels used by filters and presets.
  • Hide/Unhide: Exclude or restore entries from the shared view.
  • Share Preview: Shows the formatted output as others will see it.
  • Copy presets: One-click formats for common audiences; respects filters and hidden items.
  • Export: Download the current selection in a chosen format for archiving or sharing.

Tips

  • Start by tagging a few representative entries; presets work best when entries have consistent Audience and Category tags.
  • If an AI summary is off, edit it once—your changes are saved and used in future copies/exports.
  • Use Hide for internal refactors or dependency bumps you don’t want to broadcast.
  • Set the date range to the last sprint or release window to create focused updates fast.

Was this page helpful?

Let us know if you found what you were looking for.

Related articles

DocumentationAccount and email preferencesUse Account settings to control which product emails Moxie Docs sends you, and to permanen
DocumentationAsk this codebaseAsk this codebase lets you ask natural‑language questions about the repository connected t
DocumentationChangelog timeline and overridesThe Changelog page keeps a running log of what shipped in a repository — merged pull reque
PreviousAsk this codebase
Next Changelog timeline and overrides

On this page

  • Overview
  • When to use it
  • How to use it
  • Options and settings
  • Tips
Changelog

Powered by Moxie Docs

Overview

Changelog from PRs turns your merged GitHub pull requests into a clean, shareable changelog. It automatically summarizes each merged PR, lets you tag entries for different audiences or categories, and gives you controls to edit, hide, copy, or export updates. It’s for anyone who needs to keep teammates and stakeholders up to date without reading every diff.

When to use it

  • Share what changed in your repo after a sprint or release.
  • Create audience-specific updates (e.g., Engineering, Product, Support).
  • Prepare a weekly/monthly update you can paste into chat, email, or docs.
  • Filter out noise and hide internal-only changes before sharing.

How to use it

  1. Open Dashboard → Changelog for your repository.
  2. Select a date range at the top to choose which merged PRs to include.
  3. Review AI‑summarized entries in the list. Each entry shows the PR title, merged date, and a short summary.
  4. Edit an entry by clicking Edit. Update the title or summary to match your voice, then click Save.
  5. Apply tags by clicking Tags on an entry. Choose one or more Audience and Category tags so teammates can filter. Click Done to apply.
  6. Hide noise by clicking Hide on any entry you don’t want in the shared view. Hidden items are excluded from copy and export.
  7. Filter the list using the Filters panel (e.g., Audience, Category, Author, or Status) to refine what will be shared.
  8. Preview the changelog with the Share Preview toggle to see exactly what others will receive.
  9. Copy updates by clicking Copy and choosing a preset (e.g., “All entries,” “Product update,” “Support notes”). The formatted text is placed on your clipboard.
  10. Export by clicking Export and selecting your preferred format (e.g., Markdown, CSV). The export includes only the visible, filtered entries.
  11. Share your copied or exported changelog with your team in your usual channels.

Options and settings

  • Date range: Limits which merged PRs are included in the list and in any copy/export.
  • Filters: Narrow entries by Audience, Category, Author, or Status (e.g., hidden/visible).
  • Edit: Opens a summary editor for the selected entry; changes affect copy/export.
  • Tags: Assign Audience and Category labels used by filters and presets.
  • Hide/Unhide: Exclude or restore entries from the shared view.
  • Share Preview: Shows the formatted output as others will see it.
  • Copy presets: One-click formats for common audiences; respects filters and hidden items.
  • Export: Download the current selection in a chosen format for archiving or sharing.

Tips

  • Start by tagging a few representative entries; presets work best when entries have consistent Audience and Category tags.
  • If an AI summary is off, edit it once—your changes are saved and used in future copies/exports.
  • Use Hide for internal refactors or dependency bumps you don’t want to broadcast.
  • Set the date range to the last sprint or release window to create focused updates fast.