We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I've configured my commits' subject to be in the format as JIRA-9999 | <type>(scope): <description>
JIRA-9999 | <type>(scope): <description>
When running semantic-release no releases are detected. Using conventionalcommits preset for the @semantic-release/commit-analyzer
conventionalcommits
@semantic-release/commit-analyzer
E.g. commit message JIRA-9999 | feat: test
JIRA-9999 | feat: test
Here's my config in package.json
"config": { "commitizen": { "path": "./node_modules/@digitalroute/cz-conventional-changelog-for-jira", "jiraMode": true, "jiraPrefix": "JIRA", "jiraLocation": "pre-type", "jiraAppend": " |", "exclamationMark": true } },
Attempted: different that works on matching the string but headerPattern RegEx in the parserOpts for the config of @semantic-release/commit-analyzer
headerPattern
parserOpts
RegEx - /(\w*)(?:\((.*)\))?!?: (.*)$/gi
/(\w*)(?:\((.*)\))?!?: (.*)$/gi
If the jira position is moved, e.g. pre-description - semantic-release works fine
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I've configured my commits' subject to be in the format as
JIRA-9999 | <type>(scope): <description>
When running semantic-release no releases are detected. Using
conventionalcommits
preset for the@semantic-release/commit-analyzer
E.g. commit message
JIRA-9999 | feat: test
Here's my config in package.json
Attempted: different that works on matching the string but
headerPattern
RegEx in theparserOpts
for the config of@semantic-release/commit-analyzer
RegEx -
/(\w*)(?:\((.*)\))?!?: (.*)$/gi
If the jira position is moved, e.g. pre-description - semantic-release works fine
The text was updated successfully, but these errors were encountered: