Changelog Formatter processes repository-related text directly in the browser. It turns the supplied input into a structured, reviewable result while keeping the original details visible enough to audit. Use the included sample to confirm the expected format, then replace it with data from your own workflow.
The output reflects the fields and conventions that can be derived from the supplied text. Counts and warnings are calculated from the parsed result rather than estimated from repository history.
All processing stays in the browser tab. No repository credentials or network request are required.
# Changelog ## 1.2.0 - 2026-07-18 ### added - cursor pagination ### fixed * expired token handling ## [1.1.0] ### Changed - Legacy endpoint warnings
Run the sample to see the exact generated output and calculated metrics.
The parser works on plain text and uses deterministic JavaScript rules tailored to Changelog Formatter. It does not execute Git commands or inspect a local repository.
Formatting can vary between Git aliases, hosting platforms, and team conventions. If a custom format is not recognized, convert it to the sample structure or verify the result manually.
Use the structure shown in the built-in sample; unsupported lines are reported or placed in a fallback group.
No. The page processes text locally and does not connect to a remote repository.
Yes. Copy Output and Download both use the generated result.
Check hashes, scopes, issue references, version recommendations, and any warning shown beside the result.
No. Use it as a preparation and inspection aid alongside Git, tests, and repository policy.
| Input | Plain repository text |
|---|---|
| Output | Keep a Changelog |
| Execution | Local browser |
Explore parsers, checkers, generators, and release utilities for repository workflows.
View category