v 22.214.171.124, Windows 10 x64
I can't figure out how to use SourceTree anymore.
Staging hunks and then commiting is commiting the entire file.
I thought at first that I had accidently staged too much.
But this is repeatable.
Seems to be in either File Status view or Log/History view.
Once, after I staged a hunk, the staged and unstaged sections worked as expected. When I click on a file in unstaged, I see only those hunks that have NOT been staged. Click on a file in staged, I see only those hunks that HAVE been staged. But then click commit, review the file and all hunks are there.
Commit and all hunks are commited.
Later, the behavior changed.
After staging hunks, clicking on a file in both the staged and unstaged sections showed exactly the same hunks. I could not distinguish between staged and unstaged hunks.
The only workaround I could find was to discard all the hunks I wanted to keep, commit the rest, then in the IDE save the file to disk to get the dscarded hunks back.
Here is one issue.
The rest will have to wait until I have legitimate changes to commit.
2 hunks show changes.
Stage the second hunk.
Select FlowControl.UnitTest from the unstaged list.
Correctly shows only the first hunk.
Select the file under FlowControl.UnitTest from the staged list.
Correctly shows only the second hunk.
Select the FlowControl.UnitTest folder from the staged list.
Incorrectly shows only the first hunk, which was NOT staged.
A vulnerability has been published today in regards to Sourcetree for Windows. The goal of this article is to give you a summary of information we have gathered from Atlassian Community as a st...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event