Allow specifying some templates for CHANGELOG generation

Hi,

I noticed that CHANGELOG is not generated properly when I’m using my company’s bitbucket server. It would be nice to have a possibility to specify a template for generating e.g. compare-changes or commits URLs.

I’m aware that this issue would need to be propagated to few projects underneath, but I think it’s worth it.

[tmorehouse]

I’m having a similar issue, and would love to be able to specify a template for the change log entries.

Currently is produces invalid (in the sense of semantic markup) heading level nesting (i.e. # instead of ##, and nesting ### directly under a #).

The change log should only have a single # heading at the top, all versions should be ## headings, and change types (i.e. docs, fixes, features, etc) should be ### headings

As well, the heading IDs, which are auto-generated from the release version, start with a number, which in HTML spec is invalid.

The auto IDs generated for ### headings are identical for each version (i.e. fix, feature, etc), which makes it hard to link to a specific section.

Currently we have to use a hook method and run the changelog through sed (or replace) to fix these issues… would be nice to be able to fix them before the change log is generated via templates.

[phrohdoh]

Customizing per-version headers would be useful, too (e.g. to not have the date which makes linking to a particular version in the changelog dependent upon knowing the release date as well as the version).