Hi
As reported here https://answers.atlassian.com/questions/15281655/answers/15281680
it is possible to commit changes without having seen them.

Imagine you have a lot of changes in a file.
Then not all are shown because of Tool->Options->Diff->Internal Diff View-> Internal Diff View Count-> set to 500 (default). There seems to be good reason for this (performance). I understand that, you cannot say SourceTree is "snappy" to say it mildly.

But, this opens a trap.
Scenario:
You are about to commit a bunch of files and review them with SourceTree's FileStatus diff display. You scroll through the changes. BUT SourceTree does not show you changes 501 and later!! You think "ok, I can commit this file" but you should perhaps not because change 7xx is critical but you did not noticed it !

Feature Request (proposal):
Do not limit the number of shown diffs to begin with. It's just wrong. If a file with many changes appears, show a dialog noticing the user that he can limit it for performance reason. The dialog should optionally contain a "don't show this dialog again" checkbox.
After setting a value, the user may have forgotten, that he has set the value once. So, there should be a status bar or floating text on the diff display bottom noticing the user that there are more changes.
Then, it would be necessary to have a "expand to all changes" or similiar button. It would be very awkward if the user has to go to options and uptick the shown diffs, commit and then downtick the number of shown diffs after commit to have his performance back.

If there is such a concern about performance, then we can assume some users have even lower limits. Which makes the problem worse.