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,554,539
Community Members
 
Community Events
184
Community Groups

How to not add files to index when applying a stash

Troy Daniels
Troy Daniels Jan 31, 2019

I used to run SourceTree 3.0 (200) on a Mac.  When I applied a stash, the changes would be made to the working copy but not added to the index, unless there was a conflict.  (That seemed strange, but rarely happened.)

I now have a new laptop, running SourceTree 3.0.1 (205).  Now when I apply a stash, the files are added to the index.  How do I get the old behavior back?

Answer
Watch
Like Be the first to like this
249 views

1 answer

0 votes
bgannin
bgannin
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Feb 04, 2019

Hi @Troy Daniels,

I'm not aware of any changes that would cause this to happen offhand. It's not an intentional change. I've asked our QA team to investigate this and make sure it's in our suite going forward.

Brian Ganninger
Principal Developer, Sourcetree

Reply

Suggest an answer

Log in or Sign up to answer
Sourcetree
Sourcetree
TAGS
AUG Leaders

Atlassian Community Events

See all events