Govind S

sorry for the delayed response @mansona but I still am unable to reproduce this error on my local, it will be very helpful if you can provide a reproduction repo...

@nnmrts if youre still up for it, you can take this up now 😄

That's actually pretty interesting, because giving the version through the `prompt` and through the `cli` should not have a `Azure` dependency. Will be a tough bug to take a look...

Sounds interesting to me. Its an easy fix, and might be useful for multiple people. @sindresorhus , thoughts on this?

True, we need to support GPG passwords for this to work. We'll wait for #618 before picking this up.

According to the [GitLab Releases API](https://docs.gitlab.com/ee/api/releases/#create-a-release), it's a post request that supports creating release notes with a `description` string in the body. Should work just like `np` current release note...

Ah, makes sense. Going down the authentication path would add quite an amount of overhead. I think we can wait and see if GitLab is interested in supporting URL's before...

@sindresorhus are you still looking for help with np ? I have previously commited to [got](https://github.com/sindresorhus/got) and would like to clean up some of the issues still present in this...

@sindresorhus Could i have permission to label issues or close or open issues? I think we can cleanup quite a few issues with the right comments and labels.

So, on further investigation, this appears to be a known [issue](https://github.com/SBoudrias/Inquirer.js/issues/293) with inquirer catching the SIGINT. The same issue also has a quick-fix for this, using a `SignalRef` and this...