#Git

Using Bitbucket from a network that does not allow ssh (port 22) connections means that doing a git push or pull using the standard git ssh remote won’t work. git remote add origin https://[email protected]/USERNAME/REPOSITORY.git Where USERNAME is your user/login name and REPOSITORY is the name of the repository you want to access. If you don’t want to enter your password every time you connect to the remote you can include the password in the remote url: git remote add origin https://USERNAME:[email protected]/USERNAME/REPOSITORY.git

By far the most popular source control system in use today is Git. It was only about 6 months ago I made the switch from subversion for my personal code projects, and the only regret I have is that I didn’t do it earlier! I’m lucky enough to experience code management at both ends of the spectrum. In my spare time I tinker with personal projects (some public but mostly private stuff). At work ‘enterprise’ would definitely be an appropriate description of our source code management. With the advent of cloud computing, source control can no longer be kept neatly behind corporate firewalls.Of course you could stick a Subversion server or Git repository in your DMZ, but really, the correct answer is hosting. There are many source-code hosting providers to choose from, but in this post I’m going to look at the two most popular Git hosting solutions: Github and Bitbucket.