• Icon: Suggestion Suggestion
    • Resolution: Fixed
    • None
    • Pull Requests
    • None
    • 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.

      The merge button on pull request does "git merge -no-ff".
      This is highly undesirable as it gives a bushy history line for no good reason.

      As it is not configurable at the moment, at least it should simply call "git merge" which allow fast forwards.

      Better yet merge behaviour and strategy should be configurable for the repository with the same default as "git merge" itself.
      And/or even allow these options for each pull request merge.

      With STASH-2810 and STASH-2753, this would make Pull Requests totally rocks.

            [BSERV-2857] Pull Request should not force --no-ff flag

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3394117 ] New: JAC Suggestion Workflow 3 [ 3615883 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: BSERV Suggestions Workflow [ 2685449 ] New: JAC Suggestion Workflow [ 3394117 ]
            Owen made changes -
            Workflow Original: Stash Workflow [ 450838 ] New: BSERV Suggestions Workflow [ 2685449 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Eddy Petrisor made changes -
            Link New: This issue was cloned as STASH-7134 [ STASH-7134 ]
            Stefan Saasen (Inactive) made changes -
            Fix Version/s Original: 2.1.0 [ 29717 ]
            Affects Version/s Original: 1.3.1 [ 28401 ]
            Assignee Original: Bryan Turner [ bturner ]
            Issue Type Original: Improvement [ 4 ] New: Suggestion [ 10000 ]
            Priority Original: Minor [ 4 ]
            Seb Ruiz (Inactive) made changes -
            Link New: This issue has a derivative of STASH-3092 [ STASH-3092 ]
            Seb Ruiz (Inactive) made changes -
            Link Original: This issue has a derivative of STASH-3093 [ STASH-3093 ]
            Seb Ruiz (Inactive) made changes -
            Link New: This issue has a derivative of STASH-3093 [ STASH-3093 ]
            Seb Ruiz (Inactive) made changes -
            Fix Version/s New: 2.1.0 [ 29717 ]
            Bryan Turner (Inactive) made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: To be reviewed [ 10026 ] New: Closed [ 6 ]

              Unassigned Unassigned
              52130ab4d90d Benny Benjamin
              Votes:
              4 Vote for this issue
              Watchers:
              22 Start watching this issue

                Created:
                Updated:
                Resolved: