How to use --commit-path about conventional-changelog

[webpro]

By convention I expect this to be commitPath

Hi @webpro,

Thanks for getting back to me.
I've also tried with commitPath without any effect. My release script looks as follows:

...
"release": "release-it  %npm_package_version% --dry-run --no-increment -r 0 --verbose --no-git.requireCleanWorkingDir",
...

And my .release-it.json config looks as follows:

{
  "git": {
    "tag": true,
    "tagName": "${version}",
    "tagAnnotation": "Release ${version}",
    "tagArgs": "",
    "push": true,
    "commit": true,
    "pushRepo": "origin"
  },
  "github": {
    "version": "${version}",
    "release": true,
    "preRelease": false
  },
  "hooks": {
    "before:init": [
      "npm run build:prod"
    ],
    "after:release": "echo Successfully released ${name} v${version} to ${repo.repository}."
  },
  "npm": {
    "publish": true,
    "private": true,
    "registry": "OMITTED"
  },
  "plugins": {
    "@release-it/conventional-changelog": {
      "preset": "angular",
      "infile": "CHANGELOG.md",
      "outfile": "CHANGELOG.md",
      "commitPath": "./src"
    }
  }
}

The generated changelog and release notes contain at least 2 entries with features (feat) that comes from other folders than the ./src-folder.

[webpro]

I don't know conventional-changelog that well. I suggest to look into their docs/source code (the programmatic API, not the CLI) to see what options/arguments it takes.

Note that a dry run does not write anything.

[webpro]

Closing due to inactivity.

[dmedinag]

remove the "./" prefix of your path and it should work :)