Add the ability to specify Conventional Changelog Options

[cecilia-sanare]

Description

conventional-changelog-cli has the ability to pass in a json file with various configuration options that are passed to conventional-changelog-core. This would be a convenient option for issue trackers and git repositories that don't follow the same standards as GitHub.

Here's an example configuration:

{
  "changelogOpts": {
    "preset": "angular"
  },
  "parserOpts": {
    "issuePrefixes": ["custom-issue-prefix-"]
  },
  "writerOpts": {
    "headerPartial": "{{version}} {{~#if date}} ({{date}})\n  {{~/if}}",
    "commitPartial": "* {{this.subject}} \n\n{{~!-- commit link --}} {{#if @root.linkReferences~}} \n  ([{{hash}}]({{~@root.repoUrl}}/{{~@root.commit}}/{{hash}})){{~else}}{{~hash}}{{~/if}}"
  }
}

[Tapppi]

As standard-version is supposed to be an opinionated tool that guides people to best practices, we have been hesitant about rampant configuration. There has been talk about allowing you to set the preset, maybe along some other options, in a package.json config stanza or maybe an argument. Forking the angular preset and setting your options there would then be the preferred method. Is this what you're looking for, or do you think allowing one to modify all options is somehow necessary (asking for opinions now, as the standard-version team has seems to have been against this idea) in this cli?

/CC @bcoe @nexdrew @stevemao

[cecilia-sanare]

@Tapppi I totally agree regarding guiding users to best practices. I'll give you a bit of information regarding the issue I'm running into.

Problem

standard-version doesn't have support for linking JIRA Issues in the changelog. (from what I can tell)

Obviously to solve this issue I only need to rewrite the commitPartial and issuePrefixes so that issues link to my JIRA instance.

I don't necessarily need to be able to modify the other options.

[patrickmichalina]

I would also like something like this for VSTS online (vnext).

Their URL structure uses commit/{{full_hash}} instead of the partial hash, for example.

This relates to issue #151 as well

[smeijer]

+1, I would like an option to not include any links. This to make it easy to generate public changelogs for a private repo.

[bcoe]

@smeijer @nick-woodward @Tapppi dusting off an old issue as I go through my giant GitHub issue backlog; I don't hate the idea of introducing a .svrc and standard-version stanza in the package.json to standard-version for controlling a few select configuration options.

I think we should make things a bit less À la cart than conventional-changelog-cli; which suffers from the paradox of choice. yargs has great built in support for this functionality.

If an issue doesn't already exist, perhaps we could open one to bike-shed some initial configuration options; mainly I think introducing options that would allow us to support platforms other than GitHub, e.g., BitBucket, would be beneficial.