talos/hack/chglog/CHANGELOG.tpl.md
Andrew Rynhard 5f996e737d chore: use a single CHANGELOG
Instead of keeping a CHANGELOG for each release in the master branch, a
single CHANGELOG should be used since it will move into release branches
anyways. This prevents us from having to keep the files in sync across
master and the release branch. This also adds better tooling for
generating the CHANGELOG.md.

Signed-off-by: Andrew Rynhard <andrew@andrewrynhard.com>
2020-04-17 11:24:48 -07:00

537 B
Executable File

{{ range .Versions }}

{{ if .Tag.Previous }}[{{ .Tag.Name }}]({{ $.Info.RepositoryURL }}/compare/{{ .Tag.Previous.Name }}...{{ .Tag.Name }}){{ else }}{{ .Tag.Name }}{{ end }} ({{ datetime "2006-01-02" .Tag.Date }})

{{ range .CommitGroups -}}

{{ .Title }}

{{ range .Commits -}}

  • {{ if .Scope }}{{ .Scope }}: {{ end }}{{ .Subject }} {{ end }} {{ end -}}

{{- if .NoteGroups -}} {{ range .NoteGroups -}}

{{ .Title }}

{{ range .Notes }} {{ .Body }} {{ end }} {{ end -}} {{ end -}} {{ end -}}