Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-7721

Automatic merge failure "more information" instructions missing step

XMLWordPrintable

    • 0
    • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      When fixing an automatic merge failure, Stash provides step by step instructions under the More information link. Our developers typically copy and paste the steps and execute locally. The problem is that Step 2 does not include a git pull. The steps are fine if the developer does not have the branch in question checked out locally. They fall down if they are switching to a (potentially stale) local branch copy.

      In the example below we would like to see a git pull before the merge in step 2.

      Example

      Step 1:Fetch the changes (saving the source branch as FETCH_HEAD).

      git fetch origin release/8.0.3
      

      Step 2: Checkout the target branch and merge in the changes from the source branch. Resolve conflicts.

      git checkout release/8.0.5 
      git merge FETCH_HEAD
      

      Step 3: After the merge conflicts are resolved, stage the changes accordingly, commit the changes and push.

      git commit
      git push origin HEAD
      

              Unassigned Unassigned
              f84cf5b2-368a-47e0-b566-1db195480c06 Deleted Account (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: