Sourcetree Not Updating Changes

To add your supply request file, do the following:

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. Navigate to your repository folder on your local system and you'll see the file you just added.

  1. From your BitbucketStationSupplies in Bitbucket, click Source to open the source directory. Notice you only have one file, supplies.txt, in your directory.

    • A. Source page: Click the link to open this page.

    • B. Branch selection: Pick the branch you want to view.

    • C. More options button: Click to open a menu with more options, such as 'Add file'.

    • D. Source file area: View the directory of files in Bitbucket.

  2. From the Source page, click the More options button in the top right corner and select Add file from the menu. The More options button only appears after you have added at least one file to the repository. A page for creating the new file opens, as shown in the following image.

    • A. Branch with new file: Change if you want to add file to a different branch.

    • B. New file area: Add content for your new file here.

  3. Enter supplyrequest in the filename field.

  4. Select HTML from the Syntax mode list.

  5. Add the following HTML code to the text area:

    We are requesting additional supplies. Please send us the following:

    • space ice cream

    • nerf darts

    • telescope light shield

  6. Click Commit. The Commit message field appears with the message: supplyrequest created online with Bitbucket.

  7. Click Commit under the message field. Current time gmt 5.

SourceTree 3.3.8 20 Jan 2020 Changes. Fixed file list not refreshing in first re-opened tab; Fixed crash when double clicking file; Fixed duplicate file appearing when checking a file; SourceTree 3.3.7 8 Jan 2020 Changes. Update version of embedded git for security; SourceTree 3.3.6 22 November 2019 Changes. Fixed new branches in the push. Open SourceTree again to test if it worked or not. That's where you went wrong. Git rebase -continue expects the changes to be in the index, but not yet committed. The argument can be used to specify a specific tree-ish (i.e. Commit, tag or tree) to update the index for the given paths before updating the working tree.

Sourcetree not updating changes to my

Are you stuck unable to update your version of Atlassian Sourcetree for Windows because when you update and restart, Sourcetree hangs?

Sourcetree Not Updating Changes

I was stuck on 3.0.17. Every time I updated (to 3.1.2), Sourcetree would restart and then… hang. Unresponsive. Unable to see if there were any new updates, unable to do anything but kill the app.

It turns out the reason for this is that Sourcetree didn’t handle monitor scaling very well. Say you have a 4K monitor set to scale to 150% - that’s when you’d see the hang.

There are two workarounds for this:

Sourcetree Not Updating Changes Online

The first option is to stop monitor scaling and switch back to 100%. Not the greatest, I know, but that’ll get you through temporarily… and it only needs to be temporary. (I’ll get there.)

The other option is to do a tweak to the Sourcetree configuration file. First, make sure Sourcetree is closed. Now go to %LocalAppData%SourceTreeapp-version like C:UserstilligAppDataLocalSourceTreeapp-3.1.2. Open the file SourceTree.exe.config. Find this line:

Update it to look like this:

When you start Sourcetree, it should be responsive.

This is the default setting in 3.1.3. If you can get yourself upgraded to 3.1.3, you won’t have to do any workarounds anymore. So if you temporarily set your monitor to 100%, take the upgrades in SourceTree up to 3.1.3 or later, then you can switch your monitor back. (Or, of course, you can tweak the configuration on your hanging version of Sourcetree until you get to 3.1.3 or later.)


Install Sourcetree On Windows

I had to upgrade from 3.0.17 to 3.1.2 and then to 3.1.3. For some reason I couldn’t just go straight from 3.0.17 to 3.1.3. YMMV.