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

CLI Won't Generate from Private Remote Repository with ssh config #326

Closed
tdrozdowski opened this issue Jul 7, 2017 · 5 comments · Fixed by #583
Closed

CLI Won't Generate from Private Remote Repository with ssh config #326

tdrozdowski opened this issue Jul 7, 2017 · 5 comments · Fixed by #583

Comments

@tdrozdowski
Copy link

If you have a config file in ~/$USER_HOME/.ssh - the g8 command line will not work properly.

Expected behavior - it would identify the proper key via the config and use that to login via ssh to GitHub

Actual behavior - authentication fails and you are asked for username and password - which never work.

The only work around I currently have is to checkout the giter8 template projects locally and then use the file:// url to get to them. Ideally this should 'just work'.

OS: Mac OS X 10.12.6
Giter8 - 0.9.0 (via brew)

@tdrozdowski tdrozdowski changed the title CLI Won't Generate from Private Remote Repository if with ssh config CLI Won't Generate from Private Remote Repository with ssh config Jul 7, 2017
@taraspogrebniak
Copy link

taraspogrebniak commented Jun 8, 2018

I have the same problem when try to point g8 (version 0.10.0) or sbt new (sbt version 1.1.6) command using ssh url to the private remote repository. However git clone works properly

@johnnycaol
Copy link

I have the same problem when try to use g8 (version 0.11.0) or sbt new (sbt version 1.2.8) command to create a template from a private remote repository. It asks for username and password, but never worked even though the username and password are correct. Shouldn't it use ssh config instead by default?

@devstuff
Copy link

If you've enabled 2FA on your account you'll need to create a personal access token and use that token's value instead of a password.

@CedricAgoda
Copy link

Not sure it's the same issue, but when I run

cs foundweekends/giter8

I get the error:

Github responded with HTTP 403 Forbidden.
You may need to generate a github access token.
see https://help.github.com/articles/creating-an-access-token-for-command-line-use/

It works fine if I remove the ~/.ssh/id_rsa file.

@TonioGela
Copy link
Member

TonioGela commented Jun 10, 2021

@CedricAgoda and @devstuff, can you please test this fix? Instructions are provided, and you just need coursier and sbt to build it.

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

Successfully merging a pull request may close this issue.

6 participants