Govind S

@glennreyes that's interesting, how did it fail the first time? It worked the second time without any setup changes, right? Do you have any additional log we can use to...

 I think we already have an option for this for pre-release in the ui, but alternatively there is a `--tag` option in the np docs. Is this option not...

The error seems to be related with not having an upstream branch. Could you give us any more information on that?

On further investigation, it looks like `np` does publish the right file. However, the root of the project is still the `package.json` which started the call. You should not think...

@sindresorhus , i suggest we change the readme sligthly to stress this is the use case. I can see where the confusion could arise, I had the same doubt when...

`np publish contents=./../..` should do exactly the same thing as `npm publish ./../../` does. The contents folder will only be taken into consideration while publishing only ie when `np` internally...

 I tried to re-create this issue, and for me when the branch was missing a remote, `np` skipped that step, and went on to open the release draft and...

I think yours is similar to #452 . Did you try the solutions posted there? Looks like `np` is failing when trying to parse your git logs. Also, if you're...

That is a very weird error, I have not seen this anywhere I've used `np` on my Mac. I tried multiple times releasing new packages with np because of #613...

>I had also forgotten to create a remote repo This would definitely cause `np` to error, but still, your error sounds weird. Remote does not exist is handled within `np`,...