Changelog

Loading…

All tools › The repository's own files

Changelog

Commits grouped by the kind of change, with the breaking ones on their own at the top.

It runs entirely in this browser tab: the code you paste is never uploaded, and nothing here is executed, built or fetched — it is read and something else is written. Open your browser's network panel and try it.

What it takes

One commit subject on each line, written type(scope): description — feat, fix, docs and the rest, with ! before the colon for a breaking change.

An example

feat(basket): remember the last order
fix: total was wrong with a coupon
feat!: drop the old address format
chore: bump the linter
docs(readme): explain the ports

Settings

Version
The heading this set of changes goes under.
Date
Left empty, no date is written.
Show the scopes
The part of the code a change touched, where the commit named one.
Drop the chores
The entries nobody reading a changelog is looking for.

How to use it

  1. Paste your text into the box above, or open a file.
  2. Adjust the settings beside it until the result is what you wanted.
  3. Copy the result, or save it as a file. The result updates as you type.

Questions

Is my code uploaded anywhere?
No. The whole application is carried as WebAssembly and runs on your own device. That matters here as much as anywhere: a curl command pasted out of a terminal has a live token in it, a stack trace has your customers' identifiers in it, and a configuration file has a password in the middle of a connection address.
Does anything here run what I paste?
Never. The command explainer explains and does not execute; the Dockerfile reader reads and does not build; the request builder writes a command and does not send it. Each tool says so on its own result, and each says what that costs it — a linter that did not build the image cannot tell you the image builds.
Will an escape survive a round trip?
Yes, and there is a test that says so: every language's escaper has its unescaper beside it, and an awkward string with quotation marks, backslashes, tabs, a null and an emoji in it goes through both for every language on every run of the test suite.
Why does it refuse a pattern instead of matching nothing?
Because matching nothing looks like an answer. The glob matcher reads a stated subset — the stars, the question mark, character classes, brace lists and a leading negation — and a pattern using anything else comes back named rather than quietly matching none of your files.

Other tools for the repository's own files

Read a patch
A unified diff as what changed, file by file, with the added and removed counted.

Git commands
The command for the thing you meant, with the ones that throw work away named.

Semantic versions
Versions read, sorted and tested against a range — with the pre-release rule the right way round.

Ignore rules
Rules from templates, and a path tested against them by the rule that wins — the last one.

Choose a licence
Four answers and a licence, with the short ones in full and the long ones pointed at.

Readme badges
Badges drawn here as SVG rather than fetched from a service that may go away.

All forty tools