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

Orchestrate pull requests "merge-ready" state across multiple repositories

    XMLWordPrintable

Details

    • 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

      Pull requests along with build integration steps work great in Stash. However, currently a pull requests visibility is only in the repository where it is created.

      In our current project, we have multiple repositories and there are times when some of the repositories move together. The number of repos that move together is dependent upon the feature being worked upon and it sometimes is an overhead keeping track of pull request across projects that need to be approved at the same time.

      An example is that we have a JAVA API , a monitoring codebase and database modules. For a feature that requires changes in all the codebase , we want a mechanism of saying that the pull requests across the 3 repositories can only be merged only when all the 3 pull requests are in merge-ready state(review done, all build and tests pass, no merge conflicts etc)

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              58b44a7fb4a3 Biswajit Mishra
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: