IT:AD:SSH:HowTo:Configure for BitBucket

Probably the same for most scenarios.

The reason to use SSH/ rather than HTTPS/ for Git/ on BitBucket/:

You can use either secure hypertext transport protocol (HTTPS) or secure shell (SSH) to connect to Bitbucket. HTTPS requires you to enter a username/password each time you connect to the Bitbucket server, for example, when you push your changes. HTTPS is suitable for situations where you work with Bitbucket infrequently and make few code changes. However, if you do most of your coding with a Bitbucket hosted repository, you'll want to set up a SSH connection. After you configure SSH, Bitbucket no longer requires you to authenticate each remote communication with a username/password combination.

Src: https://confluence.atlassian.com/display/BITBUCKET/Set+up+SSH+for+Git

See Process

* https://confluence.atlassian.com/display/BITBUCKET/Set+up+SSH+for+Git * http://www.jeremyskinner.co.uk/git-on-windows/