Closed efuturetoday closed 5 years ago
This is defined by the commit
property passed to the conventional-changelog context.
By default conventional-changelog set it to commits
but we set it in our default to commit
for GitLab.
This value can also be set via this plugin commit
option.
I guess you must have something somewhere that set that value to dev
instead and override both defaults.
Hello pvdlg,
thank you for your fast response. That is a good catch for me - now I know which property controls the commit links. The strange thing is I do not modify the semantic-release context in any way and just using the official plugins for it. Side note: The @semantic-release/changelog
plugin does indeed generate a correct changelog where the links to the commits are correct.
@semantic-release/changelog
doesn't generate any changelog it just write the text generated by semantic-release/release-notes-generator
into a file.
The changelog text we add to the GitLab release and the one we write in CHANGELOG.md
is strictly the same. If you see a difference between those two it means GitLAb change it on its side.
@pvdlg it does make sense for me that the semantic-release/release-notes-generator
does generate the changelog and the other plugins just consumes it. I will do a little test on my side and see if the @semantic-release/gitlab
does send the right markdown to the gitlab backend. But I guess it will be fine. dev
is the default branch for my repository. So it's possible, that Gitlab does process the markdown in any way and modify it. I will report the results here. Thank you for pointing this out!
You can close this issue. It is obsolete. Gitlab receives the correct changelog and modifies it. I will investigate further on Gitlab. Thank you for your time and fast response!
Hi @pvdlg @efuturetoday I have this same issue but with bitbucket, my commits links in the release notes and changelog look like:
https://bitbucket.org/my-workspace/my-repo/commit/commitnumber
but it should be:
https://bitbucket.org/my-workspace/my-repo/commits/commitnumber
notice it should have s in commits, I notice here it is well configured https://github.com/semantic-release/release-notes-generator/blob/c4963f573930df1b5352ef38d3bc2c58286a9fb3/lib/hosts-config.js#L12
but why is my config not applying it? Am I missing something like maybe setting it up in releaserc.json file? Let me know if you need to see my .releaserc.json file or anything, thanks
Hello all,
first thanks for your awesome work! Currently, we are using a selfhosted Gitlab instance to manage our internal source codes. I have a npm-package that is using semantic-release in order to create a Gitlab release. The problem is that the release-notes have wrong commit links.
Every commit is like this
/binary-factory/wp-theme-binary-factory-ci-test/dev/6ebe4ac
but it should be/binary-factory/wp-theme-binary-factory-ci-test/commit/6ebe4ac
.Here is my package.json:
Do you have any clues what is the problem here? Thank you in advance for your time!
Best regards Oliver Haase