You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using a .versionrc file to specify options, and this is taken into consideration by standard-version (I checked this by setting the "feat" commit type to hidden and it worked).
# Changelog
All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.
## 0.1.0 (2019-07-22)
. . .
I would've expected the first line to be
# This header is not used
I'm using standard-version 6.0.1.
The text was updated successfully, but these errors were encountered:
@jbottigliero thanks for your quick and helpful replies (on this issue and the other one I filed). I've just tried the "feat-header-support" branch from #364 and it does indeed work as expected :-).
I'm using a .versionrc file to specify options, and this is taken into consideration by standard-version (I checked this by setting the "feat" commit type to hidden and it worked).
However, the "changelogHeader" or "header" options are ignored. I wasn't entirely clear whether the option should be specified as "changelogHeader" (as the standard-version README says you can put command-line options into the file) or "header" (as per the conventional-commits-config-spec 2.0.0). Either way, it doesn't seem to set the header in the generated CHANGELOG.md file.
Example .versionrc:
The CHANGELOG.md file begins...
I would've expected the first line to be
# This header is not used
I'm using standard-version 6.0.1.
The text was updated successfully, but these errors were encountered: