IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • Pull Request - Merge
    • 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.

      I would like to be able to configure server-side auto-merging on a per-branch basis.  For instance if I have the following branches:

      Foo
      FooB
      FooC

      Any MR merged into Foo, I want to automatically merge into FooB, and then that merge cascade into FooC.

      If there were a setting where I could say:

      Auto-forwarding branches:
      Foo -> FooB
      FooB -> FooC

      And Bitbucket would take care of it.

      If the merge can’t be done without conflict, it would be cool to create a MR and assign it to whoever submitted the initial merge that triggered the auto-forward.

      I noticed that Bitbucket claims to have automatic merging, but it is too limiting since your branches have to be named in a particular way that would not make sense for our development environment.

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

              • Icon: Suggestion Suggestion
              • Resolution: Duplicate
              • None
              • Pull Request - Merge
              • 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.

                I would like to be able to configure server-side auto-merging on a per-branch basis.  For instance if I have the following branches:

                Foo
                FooB
                FooC

                Any MR merged into Foo, I want to automatically merge into FooB, and then that merge cascade into FooC.

                If there were a setting where I could say:

                Auto-forwarding branches:
                Foo -> FooB
                FooB -> FooC

                And Bitbucket would take care of it.

                If the merge can’t be done without conflict, it would be cool to create a MR and assign it to whoever submitted the initial merge that triggered the auto-forward.

                I noticed that Bitbucket claims to have automatic merging, but it is too limiting since your branches have to be named in a particular way that would not make sense for our development environment.

                        Unassigned Unassigned
                        4c762d6af390 Corey Steele
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        3 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Unassigned Unassigned
                            4c762d6af390 Corey Steele
                            Votes:
                            0 Vote for this issue
                            Watchers:
                            3 Start watching this issue

                              Created:
                              Updated:
                              Resolved: