Create
cancel
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: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
Celebration

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

Join now to unlock these features and more

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Get started Tell me more
Atlassian Community about banner
4,456,630
Community Members
 
Community Events
176
Community Groups

Diff for staged/unstaged changes

Edited
Geißler, Daniel
Geißler, Daniel Jun 19, 2019

I used to use the Version 1.8 of SourceTree for a long time but recently updated to 3.1.2.

While most of the changes are nice, I noticed that the SourceTree Diff View does not distinguish between staged and unstaged changes while merging.

On normal editing hunks or lines can be staged and unstaged at will and when selecting the staged or unstaged version of the file one will see only the staged or unstaged modifications.

Today I realized this is not true while merging. When I start a merge, regardless if the staged or unstaged file is selected the full diff is shown in the diff view.

Did I miss a option or is this possibly a bug?

SourceTree 3.1.2, git 2.21.0.windows.1 (same for 2.22.0.windows.1)

Answer
Watch
Like Be the first to like this
387 views

1 answer

1 accepted

0 votes
Answer accepted
Mike Corsaro
Mike Corsaro Atlassian Team Jun 21, 2019

Hello! This is 100% a bug (good catch!) and I will file an issue for it ASAP. It will be fixed for the next release (3.2) which should be rolled out in the next few weeks.

 

Thanks for reporting this!

View More Comments
Ryan Liu
Ryan Liu Jun 06, 2022 • edited

The problem is back. I see this problem in version 3.4.8 and 3.4.9 on Windows 11 Enterprise.  But no problem in version 3.4.6. 

Like
Reply

Suggest an answer

Log in or Sign up to answer
Sourcetree
Sourcetree
TAGS

Atlassian Community Events

See all events