Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
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

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.

Atlassian Community about banner
4,456,634
Community Members
 
Community Events
176
Community Groups

So many checkboxes, so little time

A recent update to SourceTree gave us a checkbox next to not just files to commit, but also next to globel effect entries like Staged files and Unstaged files. When you uncheck them entries appear to disappear. If you had the preference "confirm before adding/removing files" checked, SourceTree would pop a foreground alert asking if you meant what you just did, for each and every individual file. Normal OS X style Multiple select doesn't appear to work, so you can't select a bunch of files and then check one, you have to use the "Staged files" and "Unstaged Files" entries for that. And sometimes the app gets confused and loses some of the changes if you have the confirm option turned on; they come back when I disable the confirm option.

What does this change improve? I see how clicking on the Unstaged files checkbox affects many files, but the relationships aren't immediately obvious and it took a bit of experimentation to figure out what you folks are doing. There's no horizontal differentiation between the Staged/Unstaged entries and the affected files; shouldn't the file entries, including checkboxes, at least be indented?

4 answers

I loved the behavior of the checkboxes... you check a file in Unstaged, it moves to Staged. Then vice-versa. That made perfect sense. That's how I selected certain files to be staged or unstaged. The relationships were completely obvious because Unstaged was always on top of Staged, and I could see them move back and forth. Even if there's more files than would fit in each section, I could tell that the list changed. The number of files you've changed isn't SourceTree's issue, that's yours.

Now, I have to click to select each file, then hit the spacebar or click a button to move them... which is more steps and still removes them from one list and puts them on the other. For some reason this is only required on Windows; the Mac version has the checkboxes, which I used often.

I'm not understanding the complaint here or the change... the exact same thing happens when you stage/unstage, it's just more steps now. The checkboxes made things obvious and easier.

Had to up vote just for the title

0 votes
Seth Rising Star May 07, 2014

See if this blog post clarifies the behavior.

Is there a way to comment on how your software works without having to word it as a question?

Seth Rising Star May 07, 2014

This isn't stack exchange, you probably won't have your post locked if it isn't a question.

On the other hand, most members of this site are Atlassian users - the devs are far too busy to read all of the questions. If you have a specific request for a change, you can post it at jira.atlassian.com, or vote up an existing bug report/feature request if there is one already making the same point.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events