No "Tools" item in SourceTree main menu??

Question

I can't find "Tools" in the Sourcetree menu.

I am looking for it because in the FAQs — http://www.sourcetreeapp.com/faq/ — under the question, "How do I set up SSH keys for authentication?", Step 1 is listed as "From the SourceTree menu, select Tools > Create or Import SSH Keys". However, in my menu I don't see "Tools", "SSH" or "Import" anywhere. Can someone please clarify? I

I want to Import my SSH key using putty so I can access a remote repo.

Help appreciated.

Thanks!

augustbelhumeur · Answer

Does anyone have an answer to this? There's still no "Tools" option on the top menu bar on mac and it comes up as the answer to many different bugs or questions in forums.

knichols · Answer

You have no idea about the Mac?  I do not see tools on the Mac either.

Mark Eissler · Answer

I came across a mention of the Tools menu as well while digging for an answer the other day. There is no Tools menu for the OSX SourceTree app as far as I know. I never recall seeing one.

Now you'd think that under the repo Settings (the cog at the top-right of the screen) would, under the Security tab, expose that option that Windows users see under the tools menu. But it doesn't. Sigh.

So I believe on OSX you're just stuck with managing keys the regular way. Which seems un-Mac-like but it's pretty much the way we've doing it all these years, that is, using ssh-keygen from the command line. Here are a couple of links that might be helpful:

Generating SSH Keys (via Github)

Generating Your SSH Public Key (via git-scm.com)

Now this begs the question on how to bind different keys with different repos. Since I don't use the Windows version I don't know if there's support there in SourceTree to help. On OSX, you could just also do this manually using an .ssh/config file:

Automatically use correct SSH key for remote Git repo

Specify an SSH key for git push for a given domain (via stackoverflow)

Tell git which private key to use (via superuser.com)

Not has handy as a UI, but then if you also spend time using git on the command line, as most OSX users do, then configuring this manually is possibly a better solution anyway.