Docs, for Moxie Docs

Changelog timeline and overrides

2 min readUpdated

Overview

The Changelog page keeps a running log of what shipped in a repository — merged pull requests and direct commits, summarized and split by audience. Review each entry, edit anything that reads wrong, and publish it to your repo's public "What shipped" page.

When to use it

  • You want a plain-English history of what changed, not a raw commit log.
  • You need to review AI-written summaries before they go public.
  • You want to filter history down to what a specific audience cares about.
  • You want to share a set of recent changes somewhere other than the changelog page itself.

How to use it

  1. Open the Changelog page for your repository.
  2. Filter by Publish status — Review, Published, Unpublished, or All — to find the entries you need.
  3. Filter by Audience — All, External, or Internal — to see changes relevant to a specific readership.
  4. Group and filter further using Group by, Category, and the date range controls.
  5. Review a draft entry. Entries awaiting review are flagged; open one and edit the summary if it doesn't read right.
  6. Publish or unpublish entries individually, or select several and use the bulk actions when in Review mode.
  7. Copy entries elsewhere using the copy menu at the top: Markdown, Slack / Discord, or Plain text — all copy straight to your clipboard.
  8. Include archived entries with the "Include archived" checkbox if you need to look further back.

Options and settings

  • Publish status: Review, Published, Unpublished, or All.
  • Audience: All, External, or Internal.
  • Group by / Category: Change how entries are organized and filtered.
  • Link PRs: Toggle whether entries link back to their source pull request.
  • Include archived: Show entries that have moved out of the default view.
  • Copy formats: Markdown, Slack / Discord, or Plain text — copies the current view to your clipboard.

Tips

  • Low-confidence summaries are flagged for review — check those before publishing rather than trusting them by default.
  • Editing an entry only changes how it reads; it doesn't change the underlying merged PR or commit.
  • Use Audience filtering before you copy or share a changelog snippet, so internal-only entries don't leak into an external update.

Was this page helpful?

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

Related articles

DocumentationSet up your public knowledgebaseThis guide walks you through turning a connected repository into a public help center on y
DocumentationWorkspace onboarding and invitationsUse workspace onboarding to bring your team into Moxie Docs so everyone can work from the
DocumentationUse Friday Recap and CleanupFriday Recap gives you a simple weekly summary of what changed in your docs and what needs