Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • TortoiseGit TortoiseGit
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 380
    • Issues 380
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 16
    • Merge requests 16
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • TortoiseGitTortoiseGit
  • TortoiseGitTortoiseGit
  • Issues
  • #2492
Closed
Open
Issue created Aug 02, 2015 by Sven Strickroth@mrtuxOwner

ssh key not used for new remote after clone

By yves.goer... on April 23, 2015 10:52 (imported from Google Code)


What steps will reproduce the problem?

  1. Clone a repository through ssh, select your ssh key, enter a different name for the remote
  2. Open the settings and select the one remote you just cloned from

What is the expected output? What do you see instead?
The initially used ssh key should be stored in the remote entry. But it's not. This makes any push fail until you manually enter the same ssh key file again.

What version of TortoiseGit and msysgit are you using? On
what operating system?
TortoiseGit 1.8.14.0 (C:\Program Files\TortoiseGit\bin)
git version 1.9.5.msysgit.0 (C:\Program Files (x86)\Git\bin)
Win dows 7 SP1 x64

Please provide any additional information below.
I think this used to work at some time? Not sure. Maybe entering a custom remote name is part of the problem. Since I found that it's possible to rename remotes right away, I always do so. Before, I did that afterwards. I don't like the name "origin" because it doesn't say where that is. Instead I prefer names of the actual server so I can distinguish multiple remote locations.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking