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

Merge instructions for Fork Pull Request merge conflicts have .undefined in git repository URL

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • 5.0.0
    • 4.14.1
    • None
    • None

      Summary

      When trying to merge a forked repository back to the original repository, if a conflict is detected, the instructions given for the merge are incorrect.

      Steps to Reproduce

      1. Fork a repository.
      2. Make changes to one file in the original repository after the fork.
      3. Make changes on the same file on the forked repository in order to create a conflict.
      4. Create a PR to merge back the Fork with the original repository
      5. After the PR gets created a warning panel shows the presence of a conflict and offers more information on how to solve the conflict.

      Expected Results

      The instructions show the correct steps to merge after the conflict is removed.

      Actual Results

      The instructions shown have an incorrect repository URL showed where the expected .git URL is shown as .undefined

      Workaround

      Apart from the repository URL, the instructions are still valid.

      Execute the instructions being sure to replace .undefined with .git

            [BSERV-9614] Merge instructions for Fork Pull Request merge conflicts have .undefined in git repository URL

            Owen made changes -
            Workflow Original: Stash Workflow - Restricted [ 1765061 ] New: JAC Bug Workflow v3 [ 3136943 ]
            Owen made changes -
            Symptom Severity Original: Minor [ 14432 ] New: Severity 3 - Minor [ 15832 ]
            Daniele Carcasole (Inactive) made changes -
            Affects Version/s New: 4.14.1 [ 66793 ]
            Daniele Carcasole (Inactive) made changes -
            Fix Version/s New: 5.0.0 [ 66696 ]
            Resolution New: Fixed [ 1 ]
            Status Original: Needs Triage [ 10030 ] New: Closed [ 6 ]
            Daniele Carcasole (Inactive) made changes -
            Assignee New: Daniele Carcasole [ dcarcasole ]
            Daniele Carcasole (Inactive) made changes -
            Description New: h3. Summary
            When trying to merge a forked repository back to the original repository, if a conflict is detected, the instructions given for the merge are incorrect.

            h3. Steps to Reproduce
            # Fork a repository.
            # Make changes to one file in the original repository after the fork.
            # Make changes on the same file on the forked repository in order to create a conflict.
            # Create a PR to merge back the Fork with the original repository
            # After the PR gets created a warning panel shows the presence of a conflict and offers more information on how to solve the conflict.

            !Screen Shot 2017-02-28 at 17.16.02.png|thumbnail!

            h3. Expected Results

            The instructions show the correct steps to merge after the conflict is removed.


            h3. Actual Results

            The instructions shown have an incorrect repository URL showed where the expected {{.git}} URL is shown as {{.undefined}}

             !Screen Shot 2017-02-28 at 17.14.10.png|thumbnail!

            h3.Workaround
            Apart from the repository URL, the instructions are still valid.

            Execute the instructions being sure to replace {{.undefined}} with {{.git}}
            Daniele Carcasole (Inactive) made changes -
            Attachment New: Screen Shot 2017-02-28 at 17.14.10.png [ 223083 ]
            Attachment New: Screen Shot 2017-02-28 at 17.16.02.png [ 223084 ]
            Daniele Carcasole (Inactive) created issue -

              dcarcasole Daniele Carcasole (Inactive)
              dcarcasole Daniele Carcasole (Inactive)
              Affected customers:
              0 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: