cli icon indicating copy to clipboard operation
cli copied to clipboard

cli stuck when reaching GitHub part

Open thatkookooguy opened this issue 6 years ago • 2 comments

I'm trying to run the CLI to setup a new repo on GitHub. After selecting the npm registry and logging in, once the CLI asks me for my GitHub username, it freezes. I can't even Ctrl + C out of the process.

I also tried to run the cli with all available parameters:

npx semantic-release-cli setup --npm-username=thatkookooguy --npm-token=<NPM_TOKEN> --gh-token=<GITHUB_TOKEN>

This allowed me to skip the github question straight to the What CI are you using?, but this step had the same problem (it freezes and I can't interact with it at all)

these are my versions in the package.json in case it's relevant:

"devDependencies": {
    "@semantic-release/commit-analyzer": "^6.1.0",
    "@semantic-release/git": "^7.1.0-beta.3",
    "@semantic-release/github": "^5.2.10",
    "@semantic-release/npm": "^5.1.4",
    "@semantic-release/release-notes-generator": "^7.1.4",
    "semantic-release": "^16.0.0-beta.18",
    "semantic-release-cli": "^5.1.1"
}

thatkookooguy avatar Jun 20 '19 14:06 thatkookooguy

you are passing --npm-username twice.

I can recall that happened to me too at some point, I do not remember if I had to do something or if it resolved itself. Might be a hiccup with the GItHub/Travis integration?

Can you try running the command with npm_config_loglevel=verbose npx semantic-release-cli setup. I think there is also a --debug CLI argument, give it a try, I’d have to check myself. If there is, we should document it :)

gr2m avatar Jun 20 '19 19:06 gr2m

@gr2m that's just a typo in the example I added here. When I ran the command I had one --npm-username.

Also, that was just a fix in order to skip these steps in the interactive questionnaire since it got stuck too.

thatkookooguy avatar Jul 01 '19 15:07 thatkookooguy