Uploaded image for project: 'Sourcetree For Mac'
  1. Sourcetree For Mac
  2. SRCTREE-2346

Commits missing after automatic push to remote failed

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • 1.9.3
    • 1.9.2
    • None
    • None
    • Mac OS X 10.9.2

      I have enabled the option to automatically push new commits to the remote repositories.

      When I have no network connectivity and trigger a commit, forgetting to uncheck the "push to remote" option, I get an error message that the push failed. At the same time, my working directory is clean, but I cannot see the commit I just triggered in the list.

      After restarting SourceTree, the commit appears in the list.

      This behavior can be reproduced quite simply: disconnect your machine from the network, and trigger a commit with "push to remote" enabled.

      Best regards!

          Form Name

            [SRCTREE-2346] Commits missing after automatic push to remote failed

            Yep, the log refresh trigger wasn't being called when the push failed, that's fixed for the next update.

            Steve Streeting (Inactive) added a comment - Yep, the log refresh trigger wasn't being called when the push failed, that's fixed for the next update.

            This sounds like it just missed the refresh trigger - Cmd-R would have worked too. Will check this out.

            Steve Streeting (Inactive) added a comment - This sounds like it just missed the refresh trigger - Cmd-R would have worked too. Will check this out.

              Unassigned Unassigned
              atlassian448 Jan David Nose
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: