Comments (6)
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.
from release-notes-generator.
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.
from release-notes-generator.
@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.
from release-notes-generator.
@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!
from release-notes-generator.
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!
from release-notes-generator.
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
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
SOLVED: conventional-changelog/conventional-changelog-config-spec#90 (comment)
from release-notes-generator.
Related Issues (20)
- question: link to both GH PR numbers and external issues
- Question: conventionalcommits preset with PR owner
- Defining the commitPartial voids other wirter and presetConfig options
- I need to include other commits than `feat` and `fix`. HOT 3
- Sort commit sections HOT 11
- An error occurred while running semantic-release: Error [ERR_REQUIRE_ESM] HOT 5
- wrong Gitlab issue link in release notes HOT 20
- Plugin ends up abruptly without completition or error, making other plugins not to start HOT 12
- Wrong commit link for Bitbucket HOT 3
- `release skip`-ed commits still get into release notes
- Links to PRs and Contributors list HOT 2
- `MODULE_NOT_FOUND` when running with `npx` HOT 4
- Unexpected behavior for major updates with conventionalcommits preset HOT 2
- self-hosted GitLab - no issue links in release notes
- Question: Merging pre-release branches & generated changelog
- Question: Mirror release rules to release notes generator? HOT 1
- Question: how can i gruop no-scope commits on a section in release notes generator configuration ?
- conventional-changelog-conventionalcommits v8.0.0 breaks semantic release HOT 12
- Release notes not appearing on GitHub Release descriptions HOT 2
- Deprecated dependency read-pkg-up
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from release-notes-generator.