If you wanted to use the command line to change the URL you can run the git-bash equivalent to git remote set-url from within the repo's root directory. Without Pagent you can only use one key at a time and change the settings when you need to change keys.
#Could not connect to origin gitkraken windows#
In Windows if you aren't using Pagent (from PuTTY) then you shouldn't select "use local agent" in GitKraken. Solution: If your credentials are correct, you can try signing out of the service in your default browser first, and then attempting the authentication from. switch these from to these steps are done then you can start changing GitKraken's ssh settings. This will open a sub-window that that will have two text boxes you can edit. Click options and select "Edit Origin".Hovering over this item reveals a vertical ".", that is the options button. With the remote group expanded you should see a source called Origin.This panel may be hidden, if so you'll need to click the right facing arrow symbol that should appear under the folder icon in the top left.
In the left panel expand the remote group (represented by a cloud).Luckily you can do this inside GitKraken.įirst you should navigate to your repo in GitKraken. You will first have to change the URL for your remote. Problem Jira admins are not able to connect Jira Cloud to self-hosted git servers when hosted behind a firewall or otherwise not reachable by the Git Integration for Jira Cloud indexing service. If the repo was cloned with HTTPS then no changes to SSH settings will work. When I do a pull I'm always prompted to insert the username and pass (even though I started the ssh-agent process from the git-bash).ĭon't know how I can solve this so any help you guys can provide will be much appreciated.Īlso, can't find a single way in app or online to remove/delete a repository from the app (I hope it's not obvious and I'm making a fool of myself).If the branch pushed does not exist on the remote, GitKraken Client will prompt you to name and create the new remote branch. gitkraken and changed the paths for the ssh keys to: "useLocalAgent": true, "privateKey": "C:\Users\mendo\.ssh\id_rsa", "publicKey": "C:\Users\mendo\.ssh\id_rsa.pub". Caution: Forcing a push is considered destructive because it overwrites the remote branch by replacing it with the local branch. Have messed around with the profile inside.Added the public one to my gitlab profile and can "ssh -T successfully.
#Could not connect to origin gitkraken windows 10#
I'm running Windows 10 with git-bash and have followed the tutorial on Github to generate the keys and add them to the ssh-agent. I believe the repo from Gitlab was added with https, can't find a way to change this, don't know if it's important. Configuration options / tutorials for this issue are scarce/nonexistant. I've been having a hard time getting the auth to work with ssh keys (don't want to be prompted for user and pass every time).
0 kommentar(er)
