-
Notifications
You must be signed in to change notification settings - Fork 17
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
Github Access failed on Windows #282
Comments
That's odd. What happens if you run the command manually:
You should run it from a local git repo and make sure that the repo name (right after |
I created a new local repo And got the following result: ✓ Created repository MaKaNu/TEST_TEMPLATE on GitHub
✓ Added remote git@github.com:MaKaNu/TEST_TEMPLATE.git
git@github.com: Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
E:\Git\cmd\git.exe: exit status 128 The weird thing is: The Repo was created but the commit not pushed. I had in the past multiple times issue with git on windows in cobination with OpenSSH Keys. I generally use Gitkraken for handling my configs, but with git on console it is always a hassle. |
Ok, seems like an issue with the GitHub CLI. This issues seem relevant:
Hopefully, they might also help you resolve the other issues you had with git on the command line. |
Describe the bug
Creating repository from template failed, because of missing access to github.
To Reproduce
I hopefully installed finally all necessary but not really mentioned dependencies for this template. I've started creating the template and entered every informations. For the options after the License, I choosed for every option
y
. Afterwards an empty repository is created on github but the rest of the template setup is failing. I've provided the output below. You can also see, that something isn't working correctly with the virutalenv setup. So the recreating is not my normal procedure, I put my venv usually on project path.Additional context
The text was updated successfully, but these errors were encountered: