commitizen / cz-jira-smart-commit Goto Github PK

I just downloaded Commitizen and cz-jira-smart-commit to implement them in our internal projects but I can't seem to get the latter to work.

When I run git cz I get the correct prompt (i.e. GitHub commit message, Jira Issude Id, Workflow command etc) but after filling them all in no commit is generated and the files remain in staging without being actually committed to the project.

I tried with both packages installed locally and globally but no chance, using any other wrapper (i.e. cz-conventional-changelog) everything works flawlessy. Any idea what could be causing the JIRA wrapper not to be working correctly?

My .cz.json looks like the following:

{
   "path": "node_modules/cz-jira-smart-commit"
}

Background: Most (not all) of my work has a consistent project for a number of issues at a time, so having to retype it over and over, then add the issue id number can be irritating (especially if the current project has a long ID).

Request: I'm thinking it would be good to have a config option that lets you set the project prefix so all you have to do is type the number of the issue - until you change it. Or if you are working in between projects all day you just leave the config value empty and it asks you to complete the whole thing.

I'll just leave this request here in case someone (or I) can get some work done on this and do a PR.

Thanks!

I'd like to have the time and workflow be the absolute last thing in the commit message and if there's no comment, please put it on the first line after the Jira Issue number

Hello,

I am not able to commit with this adapter for commitizen. I have used the cz-conventional-changelog adapter and that appears to work without issue. We would like to switch to this adapter as we use Jira. Any help would be appreciated.

Versions: [email protected], [email protected]
Private module and repo.
Installed as dev dependency.
cz config path is local: "path": "./node_modules/cz-jira-smart-commit"

Steps to reproduce:

1. Edit file.
2. Stage file: git stage -p (interactive hunks) or git add .
3. Commit with cz: git cz
4. Add prompt responses (Jira ticket number, comments, etc)

Expected: A clean working tree with a commit message based upon prompt responses.
Actual: Dirty working tree that has staged edits and no commit has occured.