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

Custom auto merge cascade

    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

      Hi, we here develop a desktop application and do support several past versions. We use the cascade merge option. In the development cycle we get to a point when we freeze a release candidate (RC) branch or a service pack branch (SP). We don't want to disrupt them with cascading bugfixes, but any merge to them - critical fix - should fall down eventually to master. So.

      It would be nice to have the option to shape the merge cascade. My vision is that release branches (maybe other branches as well, it depends) would have a target cascade branch specified for each of them. This way admins could control, how the cascade looks. Take out branches like RC branches if needed. It would clash with the cascade prediction system, but I think this should replace it all together. So a desired look is another page in settings, where a target cascade branch could be selected - at least for release branches.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              175ede71677c Vaclav Mares
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: