@chinesedfan Have you tested this locally and can verify this works for you? (I haven't tested this out myself, but will hopefully get to it sometime in the next few days.)

@itaisteinherz I didn't have an end-to-end package to test. Here are how I tested,

• Add some fields in package.json of np

	"private": true,
	"publishConfig": {
		"access": "restricted"
	},

• Run, node source/cli.js and select the version
• I saw it entered prerequisite-tasks stage(i.e. Git -> Check current branch) without any other prompts.

FWIW, I exported my own fork of this PR and am using it in a repository already. I know y'all ensure everything's perfect with PRs, but I needed it immediately 😂

Merging as this is ready IMO. Thanks again for working on this @kylemh 🙏🏻

Thanks! @itaisteinherz

FWIW, I'm a little afraid of the wording with private just because I went down a rabbit hole of adding private: true which actually prevents publishes entirely

FWIW, I'm a little afraid of the wording with private just because I went down a rabbit hole of adding private: true which actually prevents publishes entirely

I agree it's a bit confusing, but it's also the terminology npm uses. In this case, I think adding a note to the readme would help avoid any confusion. If you're up for doing that and creating another PR, that would be great 😉