You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I've noticed ever since the 2.x release that any changes to already committed files show up as automatically staged, which is a new and undesired behaviour for many reasons. Is there any way to disable this? I've already looked through all of the settings and searched around but haven't come across any solutions whatsoever. Thanks!
Hi
Sourcetree should not be auto-staging any files. Are there any other git related processes running?
Nope, I did figure it out though! Looks like the default staging mode for git was switched off of split view staging, which was super confusing at first. Switching to split view staging separates my current changes from what I have staged again by the looks of it. Thank you for the prompt reply though!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@minnsey I am seeing this happening, too. I have solution with number of project in it, I added about 10 new classes and modified 2, 3, but SourceTree (and git status from terminal) are showing probably about 200-300 files as being staged.
Staged area in SourceTree shows files I added/modified in my work branch and files I have not touched at all. All show with green + icon
Unstaged area in SourceTree is showing files I added or modified as it should be but they all show as yellow ... icon. No files show as not being added at all although I never issued git add command.
This has been reoccurring issue
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
This is a bit of a guess but could it be whitespace/newline handling cause so many apparent changes?
see https://www.git-scm.com/docs/gitattributes for more details
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.