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

Allow to change branch of Pull Request (support for rebase with renaming scenario)

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Duplicate
    • None
    • None
    • 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.

    Description

      As far i know, the Pull Request is simple reference in refs/pulls space. Will be nice to support follow scenario of conflicts resolving:
      1. User create Pull Request from branch 'feature' to 'master'.
      2. After review branch feature can't be merged cos of conflict
      3. User make:

      $ git fetch
      $ git checkout feature
      $ git rebase master
      # Resolve conflicts
      $ git branch -M feature/1
      $ git push origin feature/1
      

      Then (and for now) user must decline old pull request and create new one. But maybe his wand just to change reference to branch of pull request.

      This feature look like follow conflict resolution:

      $ git fetch
      $ git checkout feature
      $ git rebase master
      # Resolve conflicts
      $ git push -f origin feature
      

      Here branch is not renamed, but push -f is used. This maybe dangerous, if branch feature is on work of several developers, not a single one.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              3652ed9ede2e Alexey Efimov
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: