Compatibility with conventional changelog
See original GitHub issueThis package is not compatible with cz-conventional-changelog-with-jira
or @digitalroute/cz-conventional-changelog-for-jira
. Is the a way to befried them?
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Conventional Commits & Dynamic Changelog | by Alex Ferreira
Conventional commits is simply a way of describing our commit messages using a convention that allows them to be easily read by a...
Read more >conventional-changelog-cli - npm
Generate a changelog from git metadata. Latest version: 2.2.2, last published: a year ago. Start using conventional-changelog-cli in your ...
Read more >Tooling for Conventional Commits
Versio: A monorepo-compatible tool that updates version numbers based on conventional commits and project dependencies. It can generate tags and changelogs, ...
Read more >conventional-changelog | Yarn - Package Manager
2 (2015-06-29) ... 0.1.0-alpha.1 (2015-06-24) ... BREAKING CHANGES. This module is rewritten so API is changed and it is not backward compatible. Please...
Read more >conventional-changelog-project - npm package - Snyk
conventional -changelog-project ... Commits that follow a standard and descriptive format can be parsed programmitically to learn much about the ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
How can I use basic commitlint conventional-config with jira-config.
I need to obligate my developers to have commit in for of:
feat: PRJ-1111: subject of a change
or at leastfeat (PRJ-1111): subject of a change
. But problem with PRJ in (scope) is that scope is not obligatory by conventional commit spec.Or is there any other way to make people commit both type: and JIRA task-id: ?
If someone still searching simple solution for
feat(PRJ-1111): subject of a change
format (@GeorgeBugackov) I found for my team thiscommitlint.config.js
setup works ok:#43