anchors changelog
Build the technical changelog from the commits, release by release.
This is the TECHNICAL changelog: every feat, fix and breaking change, in the commits' ownwords, for whoever works on the code. It is not the product's release notes — for those,have an agent synthesize a product changelog from this one (`anchors guide changelog`).
A release is what the history holds between two tags. Its commits, in ConventionalCommits, say what goes where:
breaking changes a `!` after the type, or a `BREAKING CHANGE:` footer features feat bugs fixed fix with a `Bug:` footer — a defect that shipped fixes fix without it — a correction of work that never reached anyone
The other types (refactor, test, chore, …) are history, not changelog, and are left out.
By default the latest release is printed. `--from` takes every release after that tag,`--all` every one, `--unreleased` adds what came after the last tag.
`--write` writes to the file the `changelog:` block of anchors.yaml names: in `incremental`mode (the default) the releases the file does not hold yet go on its top, and what it holdsis kept as it is; in `per_version` mode each release gets its own file. The headings followthe project's `lang`, and `changelog.template` replaces the built-in template.anchors changelog [flags]| Flag | Padrão | O que faz |
|---|---|---|
--all |
list every release | |
--from |
list every release after this tag | |
--root |
. |
project root |
--to |
HEAD |
the ref the history is read up to |
--unreleased |
also list what came after the last tag | |
--write |
write to the file(s) changelog: names instead of printing |
Changelog e pull requests — família
Seção intitulada “Changelog e pull requests — família”Comandos da mesma família — o que distingue cada um:
| Comando | O que faz |
|---|---|
anchors changelog |
Build the technical changelog from the commits, release by release |
anchors commit-msg |
Confront the commit message with the format the changelog will read |
anchors pr-body |
Write the lines linking this work’s cards, in the platform’s syntax |
anchors backfill-labels |
Write into open issues the links the new version began to mark |
anchors report |
Generate reports in docs/ by perspective (cuts of what Anchors measures) |