Skip to content
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

2.8.0 doesn't make any commits #205

Open
LinusU opened this issue Apr 21, 2016 · 14 comments
Open

2.8.0 doesn't make any commits #205

LinusU opened this issue Apr 21, 2016 · 14 comments

Comments

@LinusU
Copy link
Contributor

LinusU commented Apr 21, 2016

With version 2.8.0 I can no longer make any commits, where it usually prints the new commit, it doesn't print anything at all. No commit is created, no error message is printed, and the exit code is still 0.

This is on OS X with zsh.

Reverting to 2.7.8 fixes the problem

@nelsonpjunior
Copy link

same problem here,
It seems that the prompt callback it isn't called.

@camwest
Copy link
Contributor

camwest commented Apr 21, 2016

Looks like a538dce broke the build. The upgrade to inquirer change it's API.

In 0.12.0 inquirer the interface was

function prompt(questions: any[], callback: (answers: any) => void))

Now in 1.0.2 of inquirer the signature is

function prompt(questions: any): Promise<answers:any>

https://github.com/commitizen/cz-conventional-changelog/blob/7659b955a86a13a6ce997ce0ff9bbecf9ccc54be/index.js#L32 needs to be updated to use the new signature.

@camwest
Copy link
Contributor

camwest commented Apr 21, 2016

See commitizen/cz-conventional-changelog#18 for proposed fix.

@camwest
Copy link
Contributor

camwest commented Apr 22, 2016

#206 needs to be merged before the fix will be taken.

@LinusU
Copy link
Contributor Author

LinusU commented May 13, 2016

ping @jimthedev, this still seems to be broken :( any updates?

@jimthedev
Copy link
Member

@LinusU This was merged and published. Are you using [email protected] and [email protected]? I just tested it in OSX and it seems to be working.

@LinusU
Copy link
Contributor Author

LinusU commented May 14, 2016

Hmm, I just had a colleague that made a clean install the other day which it didn't work for... I'll have to check Monday which versions he was using...

@albinekb
Copy link

Still broken @ version 2.8.1

@jimthedev
Copy link
Member

@albinekb Can you let me know what version of cz-conventional-changelog (or another adapter) that you are using?

@zacharytelschow
Copy link

I am running into the same issue.

$ npm list -g --depth=0
C:\npm
├── [email protected]
├── [email protected]
└── [email protected]

@zacharytelschow
Copy link

I installed [email protected] and updated my adapter and was able to commit.

I was unsuccessful when attempting to commit with:

@jimthedev
Copy link
Member

@zacharytelschow Those adapters probably need to implement the changes in the Inquirer 1.0 API. You can see these changes here: commitizen/cz-conventional-changelog@807b4e5d

At the end of the day we probably need to have some compatibility checking between adapters and the commitizen cli so that if you try to commit and your adapter isn't compatible with the cli you're using then you're prompted to contact the adapter author.

@LinusU
Copy link
Contributor Author

LinusU commented Jun 2, 2016

See #249 for a proposed solution for fixing this in a more long term way

@OmgImAlexis
Copy link

Since were now on version 4.x can this be closed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants