Changelog

Close the loop when you ship

Shipping a request drafts a changelog entry and notifies the author and every voter. You publish, and the people who asked hear back.

Create your workspace

One workspace, every channel, the whole loop.

What works today

  • Shipping drafts a changelog entry automatically
  • Publish entries to the public portal
  • Requester and voter notifications fire when a request ships
  • Readers can react to published entries

How it fits the loop

  1. Ship

    Marking a request shipped drafts its changelog entry.

  2. Publish

    Edit and publish the entry to the portal.

  3. Notify

    The author and voters are notified the loop closed.

FAQ

Do I write changelog entries from scratch?

Shipping a request creates a draft entry for you to edit and publish — you shape the wording, but the loop-closure mechanics are automatic.

Who gets notified when something ships?

The requester and everyone who voted are notified exactly once, and the changelog entry is published to the public portal.

See it in your own workspace.

Create your workspace