Uploaded image for project: 'Sourcetree for Windows'
  1. Sourcetree for Windows
  2. SRCTREEWIN-1813

Check for changes pending on remote before commit + push

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Won't Fix
    • None
    • Git
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      The most common mistake at our company (which recently switched from subversion) is the commit + push before doing a Pull. If you do a commit + push and there are changes that were not pulled from the remote the following things happen:
      1. Commit executes
      2. Push fails

      You naturally run a Pull and the following things happen:
      1. Your pending commit gets automatically branched away from the master branch.
      2. The pending commits from the remotes get committed to the repository.
      3. The previously created branch is automatically merged to the master branch.

      We are all expecting for an error message saying that there are pending commits on the remote and a prompt asking for a Pull before running our Commit + Push. Using tortoise svn we were making use of this feature extensively.
      Another possible solution to this problem would be to automatically run a pull before the commit + push however that might be too invasive.

      Attachments

        Activity

          People

            sstreeting Steve Streeting (Inactive)
            cddc8252806d paulcsiki
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: