Source tree how to download old files

The process is pretty straight forward, basically just the reverse of the push you used to get the supplies. Open your repository in Sourcetree, and click the Pull button. A popup appears to indicate that you are merging the file from Bitbucket to your local repository. Click OK from this box. Sourcetree updates with a description of the merged file. Now, you have finished the basic DVCS workflow clone, add, commit, push, and pull between Bitbucket and your local system. After looking through the Intergalactic Mall Magazine, you see a pair of speakers that you really want for the space station.

They are big enough to produce a good amount of sound and soft enough that the lack of gravity won't cause them to crash. The only problem is that they pretty pricey, and you need approval before you can officially add them to your list of supplies. In the meantime, create a feature branch so that you can update the supply to your request list while you wait. Then when you have approval, you just merge the requests file from the feature branch into the main branch.

Branches are most powerful when you're working on a team. You can work on your own part of a project from your own branch, pull updates from Bitbucket, and then merge all your work into the main branch when it's ready.

Our documentation includes more explanation of why you would want to use branches. Let's create a branch so that you can list the speakers in your supply requests file. Even though branches work differently between Git and Mercurial, you create them in a similar way from Sourcetree. From Sourcetree, click the Show in Finder button. The directory on your system opens. Making a change to the file by adding the following item to the list of supplies: anti-gravity speakers.

Open the view in Sourcetree and notice that your repository now has uncommitted changes. From here, everything you do is the same as you did when you added the supplyrequest file and initially committed it. If you have a Git repository, make supplyrequest.

From Sourcetree, you see that the file has been updated on the wish-list branch. Your speakers were approved! Now it's time to update the main supply list with your wish-list item. Click the Merge button. From the popup that appears, make sure the commit on your wish-list branch is highlighted. You are indicating that you want to add the commit from this branch to the main branch.

If you have a Git repository, check this option at the bottom: Create a commit even if merge resolved via fast-forward. Click OK. You have updated the supplyrequest file in your main branch with your wish-list item. Sourcetree will look slightly different based on whether you have a Git or Mercurial repository. If you have a Git repository, you are done. If you have a Mercurial repository, you will notice that you need to commit your changes.

Click the Commit button at the top. The commit message defaults to a description with "Merge. From the dialog box that appears, click the OK button to push changes to your local repository. Click the Overview page of your Bitbucket repository, and notice you can see your push in the Recent Activity stream. Click Commits and you can see the commit you made on your local system.

Notice that the change keeps the same commit code that it had on your local system. Click Source , then click the supplyrequest file. You can see the last change to the file has the commit code you just pushed. Click the file history list to see the committed changes for this file, as shown in the following image.

That was intense! Since the only file we changed was Program. If you click on it you'll see the contents of the file appear on the right below the '3'. If you examine the file in the above picture you'll notice that it's actually trying to show you how the file has been changed. Lines that are highlighted in green and have a minus sign at left edge are lines that have been removed.

Lines highlighted in green with an addition sign a plus sign at the left are new lines. When we change a line it's represented as the old line being deleted and the modified line being added. You can see this on line 9, where we changed it from. You'll notice that the Program. A 'Staged file' is a file that git will save commit , once we tell it to do so.

By allowing us to separately stage, and then commit save our files we could very carefully commit only a couple of our files if we wanted to.

In this class it's recommended that you stage all your files so you don't accidentally leave anything out. You can click on the 'Program. Just like with GitLab you must write a commit message before you're allowed to commit you change. You can do that by filling in the box that '3' points to. Once you've written a Commit Message the Commit button will be activated near the '4' arrow. Make sure that it's checked and it will not only save your changes to your local git repo but it will also push the changes back to the GitLab server where your teacher can see it and grade it.

In order to confirm that the commit was successfully pushed back to the server we'll look at the contents of the file itself. However, before we look at the file contents we can already see two clues that the commit worked. First, you'll notice that the second column in the files table lists the 'Last Update', and that Program.

Second, you can see the Commit Message in the last column above the '2' arrow. However, there's nothing quite as reassuring as seeing the newly updated contents of the file itself. Click on the word 'Program.

This does look like the changed file that saved so we know that we were able to save our changes successfully. If you looked on GitLab and didn't find your changes then you should start by retracing your steps. Make sure that you made the changes in Visual Studio, and make sure that you saved them. If the changes were made and saved then the next step is to see what SourceTree says about the project.

In that case you'll see the changed files in Visual Studio but both the Staged file and Unstaged files lists will be empty. If you examine the 'Push' button in the ribbon at the top above the '2' arrow you'll notice that there's a tiny number 1 there as well.

Otherwise, register and sign in. I was going nuts You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events. Atlassian Community logo Products Interests Groups. Create Ask the community. Ask a question Get answers to your question from experts in the community. Start a discussion Share a use case, discuss your favorite features, or get input from the community.

Turn on suggestions. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for. Search instead for. Did you mean:. Understanding how "checkout" works With the "git checkout" command, you determine which revision of your project you want to work on.

You are in 'detached HEAD' state Improve this answer. December 9, Caner Caner 3, 26 26 silver badges 25 25 bronze badges. I would suggest you to use the command line client, instead of web UI to learn git better. Suraj Muraleedharan Suraj Muraleedharan 1 1 gold badge 9 9 silver badges 25 25 bronze badges.

Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown.

The Overflow Blog. Podcast An oral history of Stack Overflow — told by its founding team. Millinery on the Stack: Join us for Winter Summer?