#USING SOURCETREE PASSWORD#

In case you’re wondering, the “Basic” authentication type uses your account’s username and password and has been deprecated by GitHub so it will stop working soon. In the popup that opens, select the “Authentication” tab and click on the “Add” button. In SourceTree, using the top menu navigate to Tools ⇒ Options. There are several ways of doing that and we’re going to use the easiest: connection over HTTPS.įirst make sure that, in your browser, you are logged in to your GitHub account.

Once SourceTree is installed we need to add your GitHub account to it. I am not sure to what extent since I don’t have a Mac, but I believe the essentials are still pretty much the same. Getting SourceTree set upīefore we start it is worth noting that SourceTree is different on Mac and Windows. While installing SourceTree, provide your BitBucket credentials and, when asked, select Git and not Mercurial (another versioning system) unless you want to give it a try.

#USING SOURCETREE FREE#

In Github, you get only public repositories on the free plan.

If you’re going to start using Git, it’s a good idea to have a BitBucket account since, unlike GitHub, they offer private repositories with their free accounts. BitBucket is a GitHub competitor from Atlassian, also makers of SourceTree.

#USING SOURCETREE INSTALL#

To install SourceTree you need a (free) BitBucket account.

#USING SOURCETREE DOWNLOAD#

If you haven’t already, download SourceTree and install it. Posted by Nour Akalay on DecemUpdated on October 8, 2020. Let’s move on to serious stuff with SourceTree. When you push the changes to your remote Bitbucket repository, those changes apply to the repository's branch.The Git and SourceTree beginner's guide to contributing to open-source projects in GitHub - Part 3 - Working with SourceTreeīy now you have learned the essential concepts you need to start using Git (part 1) and have done some forking and branching in GitHub (part 2) Going forward, all your Git commands apply to the branch. In this example, the feature branch is the branch.Ĭonfirm you are now working on that branch: Using the list as reference, choose the branch you want to checkout. Notice that it lists both the branches that are local and the remote branches on Bitbucket. You should see something similar to the following: Then, do the following:Ĭhange to the root of the local repository. On your local system, make sure you have a local repository cloned from the remote repository. Using Git to checkout a branch on the command lineįor the purposes of these steps, will refer to the name of your branch. Open the terminal on your local machine and change to the root directory of your repository.Īt the command line, enter the copied command from Bitbucket and press ENTER. Press the Check out button to display the appropriate check out command.Ĭopy the command (or choose Check out in Sourcetree if you'd rather use Sourcetree). In the repository's Branches, click the branch you want to checkout. If you're using Sourcetree, Bitbucket gives you a single button checkout. The Bitbucket interface gives you the basic command for checking out a branch. When you checkout a branch, you should already have a local clone of the parent repository. If you plan to use branches a lot or want to know more, we recommend you learn more by visiting a site or buying a book devoted to the DVCS you are using (Git or Mercurial). It merely provides a pointer to help you understand how Bitbucket supports branches. The information on this page is not a definitive guide for either Git or Mercurial.

Using sourcetree