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
The generated links for the diff and commits in the release notes are not correct when using semantic-release with Bitbucket hosted git repos, when cloning a repo using HTTPS protocol. The issue can be resolved by using SSH protocol but that sometimes requires additional effort in a CI environment, so it would be nice if both HTTPS and SSH URLs work well.
The origin of the issue is that Bitbucket adds "/scm/" in the URLs used for cloning repos using HTTPS (and they are not planning on changing this). With this, the owner of the repository is incorrectly detected as "scm" and the repository takes the value of "{owner}/{repository}" at the following line:
The preset used in the affected environment is angular-bitbucket since the default angular preset (and the others) does not generate correct links for Bitbucket (could be also adjusted by using different header in the headerPartial option for the writer).
I have tried a solution which works in my environment but I am not sure if that is valid solution for all possible use cases / URLs.
Replacing line 31 here:
Hello,
The generated links for the diff and commits in the release notes are not correct when using semantic-release with Bitbucket hosted git repos, when cloning a repo using HTTPS protocol. The issue can be resolved by using SSH protocol but that sometimes requires additional effort in a CI environment, so it would be nice if both HTTPS and SSH URLs work well.
The origin of the issue is that Bitbucket adds "/scm/" in the URLs used for cloning repos using HTTPS (and they are not planning on changing this). With this, the owner of the repository is incorrectly detected as "scm" and the repository takes the value of "{owner}/{repository}" at the following line:
release-notes-generator/index.js
Line 40 in 928e8fc
The preset used in the affected environment is angular-bitbucket since the default angular preset (and the others) does not generate correct links for Bitbucket (could be also adjusted by using different header in the headerPartial option for the writer).
I have tried a solution which works in my environment but I am not sure if that is valid solution for all possible use cases / URLs.
Replacing line 31 here:
release-notes-generator/index.js
Line 31 in 928e8fc
is providing the expected links for Bitbucket when using "angular-bitbucket" preset.
The text was updated successfully, but these errors were encountered: