-
Notifications
You must be signed in to change notification settings - Fork 794
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
feat: add ability to specify conventional changelog preset #170
feat: add ability to specify conventional changelog preset #170
Conversation
@lancecaraccioli we're having a similar conversation on lerna: My concern is that tools like https://conventionalcommits.org/ @Tapppi thoughts? |
My specific use case is that our repository is BitBucket and our issue tracker is Jira. The only other option would be to fork conventional-changlog-angular and maintain, what feels to be, a dirty copy. by allowing conventional-changlog-VENDOR to be owned by VENDOR as an external repository, with the addition of this PR then it's possible to wire up to VENDOR specific resources. |
@lancecaraccioli would love to support your use-case; so that I better understand -- does Jira have a specific commit format that it forces you to adhere to? |
@bcoe We have specific URL paths for user urls, bug links, diff links, etc. I believe I made a minor change to a template. I'll paste it here when I start work on polishing the docs for the PR |
@lancecaraccioli okay cool -- what I was coming to; was maybe we could support this use-case by passing in an appropriate template context, and making some tweaks to the template 👍 (rather than adding more configuration toggles). we could even publish a Jira preset 👓 using this new feature we've been building out in yargs: |
@lancecaraccioli I think we just need to add a couple optional parameters for specifying the issue URL, and to extend this functionality slightly: what do you think? |
Definitely need this feature! |
cleaning up some old pull requests, please feel free to reopen this conversation if you're still interested in implementing this. |
should close #169