-
-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Context attribute "compareUrl" is not working with bitbucket repository #90
Comments
After looking into source codes, I should admit that it is not easy to customize this in the current version without monkey patches. I have marked this one as an enhancement. A more extendable pattern should be adopted to design this cross-platform VCS (Version Control System) feature. |
@momocow Thanks, it would be amazing to have such a enhancement, meanwhile this is what I did on the default-handlebar template: Replaced the if/else statement with this one:
works so far but yeah I would prefer a lot more the enhancement, thanks again :) |
@momocow I was using the tool with github, but now I am trying to setup everything on bitbucket too, I notice that this on my default handlebars template (which is the same from the example but with the emojis):
works with github repository, but with bitbucket it is always entering the else, is there anyway to make it work with bitbucket too?
When I was using release-notes generator plugin I also had to do some tweaks for it to work with bitbucket like so:
Please let me know if I can do something like this to get the compare url working, the commit url was easy to fix on the commit template but the compare url not sure how to fix.
EDIT: I was reading again this https://github.com/momocow/semantic-release-gitmoji?tab=readme-ov-file#releasenotesoptions
you mention that github is currently the only repo supported but you also mention that it is possible to override the baseUrl and other values, can you please show example how to override them? Maybe this way it can work with bitbucket too
The text was updated successfully, but these errors were encountered: