-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
None
-
Affects Version/s: 1.7.3
-
Component/s: Git
-
None
-
Environment:
Mac OSX 10.9
-
Severity 3 - Minor
When committing changes, I will often select "push to remote" so changes are instantly uploaded to my remote git server. When a connection is not available, SourceTree will obviously state that the push failed. The commit seems to still be successful, but the UI does not update to show the new commit.
I would expect, even when the push fails in this circumstance, for the commit to succeed and show up in the commit history and the push badge to update and show that there are commits that need to be pushed. Instead, the UI shows no changes (no commits and no push changes). When I re-establish a connection and push changes to the server, SourceTree shows that there was a successful commit and then pushes it to the remote server. After the push, the UI successfully updates to show all commits.