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

Improve How Rescope Works for Large Instances with Tens of Thousands of Open Pull Requests

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Unresolved
    • None
    • Pull Requests
    • None
    • 18
    • 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

      The rescoping process for large instances with a large number of open pull requests, tens of thousands, Bitbucket can take longer to update open pull requests when there's a change because of the ways rescope traverses all open pull requests, and would also throw the Pull request merges fail since "New changes were pushed" error while trying to merge pull requests that have just been pushed to.

      For scenarios like these, Bitbucket should have an option to run a rescope limiting it to the project in which the push has happened or even to the repository, to allow for a better pull request update performance. 

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              a4e9a794748b Bailey Waldorf
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated: