Smart classification
Features, fixes and breaking changes are grouped with an explanation instead of an unreadable git log.
Features
Release notes your customers can actually read.
Connect GitHub once. ChangelogForge classifies changes with a reason you can verify, then lets you publish to GitHub Releases.
Approval before publishing
Team plans add a review workflow so a person can inspect the release draft before it goes live.
Built around GitHub
Connect repositories, generate a release draft and publish to GitHub Releases without a new release process.
# release-draft · example
feat: add Microsoft sign-in
fix: prevent duplicate webhooks
docs: explain release permissions
1
Commit metadataClassify the change
Ready2
Verifiable reasonReview the release draft
Review3
PublishGitHub Releases, when approved
One clickIllustrative example — not a customer result or live account data.
How it works
Connect your input
Use the product’s documented starting point rather than creating a new process.
Inspect the result
Review the example or draft, including its assumptions and limitations.
Take the next action
Publish, share or upgrade only when the verified product path supports it.
Frequently asked questions
Does every feature-branch commit use a generation?
The public product describes configurable triggers (release branch, merge, release or on demand). Verify your repository settings before assuming a quota model.
Does ChangelogForge see my source code?
Its public page says the official GitHub App uses least-privilege permissions and processes commit metadata/diffs to classify drafts. Check the current App manifest and privacy terms for your use case.
Can I inspect a changelog before signing up?
Yes. The public demo link lets you inspect an example without creating an account.