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
Currently, the conventional-changelog dependency uses repository.url in package.json by default to generate the links in the changelog.
According to the npm documentation this url should be able to be used by a VCS program, and should not be a url to a html project page.
We have the need to have different vcs and html urls. semantic-release allows the repository url to be customised.
Would it be appropriate to add a --repositoryUrl option to corp-semantic-release that can be passed to conventional-changelog?
Happy to contribute if you are happy with this solution.
Currently, the
conventional-changelog
dependency usesrepository.url
inpackage.json
by default to generate the links in the changelog.According to the npm documentation this url should be able to be used by a VCS program, and should not be a url to a html project page.
We have the need to have different vcs and html urls.
semantic-release
allows the repository url to be customised.Would it be appropriate to add a
--repositoryUrl
option tocorp-semantic-release
that can be passed toconventional-changelog
?Happy to contribute if you are happy with this solution.
@leonardoanalista
The text was updated successfully, but these errors were encountered: