Documentation menu

Your changelog page

Every connected repository gets a hosted, public changelog page. There is nothing to deploy and nothing to embed — publish an entry and the page is live.

The URL

Your page lives at:

changelogpilot.com/c/your-owner/your-repo

Link it from your app's footer, your docs, or release announcements. Until your first publish, the URL shows a "no changelog published yet" note rather than an empty changelog — the page goes properly live with your first published entry.

On Pro you can serve the same changelog from your own domain — say changelog.yourproduct.com. The platform URL keeps working alongside it, with search engines pointed at your domain as the canonical address. Setup lives in the repo's settings.

What readers see

Published entries, laid out as a timeline. Entries anchored to a release tag come first, then the rest, each group running newest first. On wide screens an index down the side links to each entry, labelled by its release tag when there is one and by date otherwise. Each entry has a stable anchor, so you can link directly to a specific entry from support replies or release announcements. Long histories are paginated, twenty entries to a page.

Feeds

Every changelog has RSS and Atom feeds with full entries, on every plan:

changelogpilot.com/c/your-owner/your-repo/rss.xml
changelogpilot.com/c/your-owner/your-repo/atom.xml

Readers can follow along in a feed reader, and tools can consume the feeds without any API token.

Making it yours

  • Themes. Pick from a set of light and dark colour themes for the public page — included on every plan. See Themes and branding.
  • Branding. On Pro you can set your own colours, upload your logo, and hide the "Powered by ChangelogPilot" badge — also covered in Themes and branding.
  • Reader subscriptions. On Pro, readers can subscribe by email straight from the page and get each entry as it publishes. See Reader subscriptions.
  • Custom domain. On Pro, serve the page from your own subdomain, as above. See Custom domain.

Each of these lives in the repo's settings.