A few small documentation things around changelog generation. (#691)
Co-authored-by: Armin Ruech <7052238+arminru@users.noreply.github.com>
This commit is contained in:
parent
5fd9bfeece
commit
c9252a1222
|
|
@ -13,6 +13,7 @@ component:
|
|||
note:
|
||||
|
||||
# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
|
||||
# The values here must be integers.
|
||||
issues: []
|
||||
|
||||
# (Optional) One or more lines of additional information to render under the primary note.
|
||||
|
|
|
|||
|
|
@ -174,7 +174,7 @@ from `.yaml` files in the [/.chloggen](/.chloggen) directory.
|
|||
Your pull request should add a new `.yaml` file to this directory.
|
||||
The name of your file can be arbitrary but must be unique since the last release.
|
||||
|
||||
During the release process, all `./chloggen/*.yaml` files are transcribed into
|
||||
During the release process, all `./.chloggen/*.yaml` files are transcribed into
|
||||
`CHANGELOG.md` and then deleted.
|
||||
|
||||
1. Create an entry file using `make chlog-new`. The command generates a new file,
|
||||
|
|
|
|||
Loading…
Reference in New Issue