How does AutoChangelog work?

AutoChangelog integrates with your GitHub repository and automatically generates changelog entries from your pull requests. When you merge a PR, our AI analyzes the changes and creates a clear, user-friendly changelog entry. You can review and publish entries from your dashboard.

Do I need to write changelogs manually?

No! That's the whole point. AutoChangelog reads your pull requests and generates changelog entries automatically using AI. You can review and edit them before publishing, but you never have to start from scratch.

What information does AutoChangelog use to generate entries?

AutoChangelog analyzes your PR title, description, code changes, and any related commits. Our AI then transforms this technical information into clear, user-friendly language that explains what changed and why it matters.

Can I edit the generated changelogs?

Yes! Every generated entry can be reviewed and edited before publishing. You have complete control over what gets published to your changelog.

What's the difference between draft and auto-publish?

In draft mode, generated entries are saved as drafts for you to review before publishing. With auto-publish enabled, entries are published immediately when generated. You can choose either mode per repository in your settings.

Which GitHub plan do I need?

AutoChangelog works with any GitHub plan, including free accounts. As long as you can create pull requests in your repository, AutoChangelog can generate changelogs for them.

Can I use AutoChangelog with private repositories?

Yes! AutoChangelog works with both public and private GitHub repositories. We securely access your repository through GitHub OAuth with the permissions you grant.

How many repositories can I connect?

The Free plan supports 1 repository. The Pro plan supports 1 repository with unlimited PR processing. The Team plan supports unlimited repositories with unlimited PR processing.

What happens if I exceed my plan's PR limit?

On the Free plan, you get 10 AI-generated changelogs per month. Once you reach this limit, new PRs won't generate changelog entries until your limit resets (monthly) or you upgrade to a paid plan.

Can I export my changelogs?

Your changelog entries are available via a public changelog page at autochangelog.com/c/[your-repo]. Each entry is written in Markdown and can be easily copied or accessed via our API.

How do I share my changelog with users?

Every repository gets a public changelog page at autochangelog.com/c/[your-repo]. You can link to this from your website, documentation, or GitHub repository. Pro and Team plans will support custom domains soon.

What happens to my changelogs if I cancel?

All your published changelogs remain accessible even after cancellation. You'll have a 7-day grace period where everything continues working. After that, repositories exceeding the free tier limit will be disabled, but your changelog data is never deleted.

Can I customize the changelog format?

Currently, AutoChangelog uses a clean, consistent format optimized for readability. Custom templates and formatting options are planned for future releases. You can always edit individual entries to match your style.

Custom Domains | Documentation

Overview

Instead of using the default autochangelog.com URL, you can host your changelog on your own domain like changelog.yourapp.com or updates.yourcompany.com. Custom domains make your changelog feel like a natural part of your product.

Setting Up a Custom Domain

To add a custom domain, go to Settings → Custom Domains in your AutoChangelog dashboard. Enter your desired domain (like changelog.yourapp.com) and click "Add Domain". You'll then need to configure your DNS to point to AutoChangelog.

Configuring DNS

After adding your domain, AutoChangelog will display the DNS records you need to configure. Follow the instructions shown in your account to set up the correct records with your DNS provider.

Verifying Your Domain

After adding the DNS record, return to AutoChangelog and click "Verify Now". DNS changes can take up to 48 hours to propagate, but usually complete within a few minutes. If verification fails, wait a bit and try again. You can use a DNS checker tool to confirm your record is visible before retrying.

SSL Certificates

We automatically provision and renew SSL certificates for your custom domain. Your changelog will always be served over HTTPS with no additional configuration needed. Certificate provisioning happens automatically after domain verification, usually within a few minutes.

Supported Domains

Custom domains must be subdomains like changelog.yourapp.com or updates.yourapp.com. We don't support apex/root domains like yourapp.com.

Multiple Domains

Each repository can have one custom domain. If you have multiple repositories on the Team plan, each can have its own custom domain. You configure the domain per-repository from Settings → Custom Domains.

Removing a Custom Domain

To remove a custom domain, go to Settings → Custom Domains and click "Remove" next to your domain. Your changelog will continue to be available at the default autochangelog.com URL. Don't forget to also delete the CNAME record from your DNS provider to keep things tidy.

Troubleshooting

If your domain isn't verifying, double-check that your DNS records match exactly what's shown in your AutoChangelog settings. Wait a few minutes for DNS propagation and try again. Make sure there's no conflicting A record for the same subdomain. Use a DNS checker tool to verify your record is visible globally.

If you see SSL certificate errors after verification, wait 5-10 minutes for the certificate to be issued. Clear your browser cache and try again, or access the page in an incognito window. Certificate provisioning is automatic but can take a few minutes.

If your custom domain shows an error page, verify the domain is still configured in AutoChangelog settings. Check that your repository is enabled and hasn't been disabled. Confirm the CNAME record hasn't been deleted from your DNS.