Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Sourcetree (for Mac) is committing unstaged files

Not sure if I am missing a setting or if this is a legitimate bug.  Whenever I commit, it also commits my unstaged files/hunks.  This is obviously very frustrating and has caused some code to be committed that I was not ready to commit or ever intended to be committed.  I have included some screenshots to illustrate a simple scenario.  Below I only intend to commit the changes for the one file ''.  As you can see I left the 2 other files unstaged as I do not intend to commit those changes quite yet.  However, after committing the changes I pulled up the commit which shows that all 3 files were committed up anyways.


Before Commit (Staging):


After Commit: 


3 answers

TL;DR - reclone your repo from scratch.

Ok I have an actual answer for this one. It was an unknown repo issue for me. Here's what I did to determine that:

1. Wiped all Sourcetree settings, and tried the same thing again - same problem happened.

2. Restored all Sourcetree settings: tried the same thing with a new test repo - could not reproduce the problem.

3. Blew away and recloned my local repo - problem went away.


I hope this helps someone out there. @Chris Burkhardt @Brady maybe this will help.

I am also having this issue on Mac, still with version 4.1.0 (237). This is maddening since it is making me look foolish to my colleagues since my commits are containing work-in-progress pieces that I never staged.


I have to ditch Sourcetree until this is fixed.

The same thing is happening to me. I am not sure how to solve it so I went back to command line and stopped using SourceTree for now.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events