semantic-release / semantic-release/release-notes-generator
Wrong commit link for Bitbucket
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 368
- Forks
- 55
- Avg merge
- 10m
- Merged PRs (30d)
- 1
Description
Hello everyone.
I would like to raise a possible issue with the generated links for the diff and commits when using bitbucket.
What is generated by default looks like this https://<BASE>/scm/<PROJ_NAME>/<REPO_NAME>/commit/<HASH>.
Bitbucket commit links look like this though: https://<BASE>/projects/<PROJ_NAME>/repos/<REPO_NAME>/commits/<HASH>.
I have tried setting the host to the correct path, but /scm/<PROJ_NAME>/ is still appended after my override.
My question is, am I supposed to define the repo URL somewhere else or is this an issue with this plugin?
Version Information:
- Bitbucket Data Center: v7.2.1
- semantic-release: 17.4.7
- git: 9.0.1
- exec: 5.0.0
- changelog: 5.0.1
Thank you in advance. Please reach out if you require further information.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how this plugin generates Bitbucket diff and commit links, using the reported /scm/.../commit/... output as the reproduction case. Compare it with the Bitbucket Data Center 7.2.1 URL format in the issue. Done means the generated links use the expected /projects/.../repos/.../commits/... paths and host overrides no longer receive the unwanted suffix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100