• Icon: Suggestion Suggestion
    • Resolution: Done
    • None
    • Git Hosting
    • 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.

      Ideally a mechanism for automatically managing repository issue and release branches using the Git Flow model, with branch creation and permissions management in Stash, and the ability to automatically create a Pull Request (See feature request STASH-2482) when work on the issue is complete.

            [BSERV-2491] Add Git Flow (branching) support

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3393863 ] New: JAC Suggestion Workflow 3 [ 3615598 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: BSERV Suggestions Workflow [ 2684474 ] New: JAC Suggestion Workflow [ 3393863 ]
            Owen made changes -
            Workflow Original: Stash Workflow [ 383442 ] New: BSERV Suggestions Workflow [ 2684474 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Norman Ma (Inactive) made changes -
            Resolution New: Done [ 17 ]
            Status Original: Open [ 1 ] New: Closed [ 6 ]

            Hi everyone,

            Thanks to everyone for voting and commenting on this suggestion. Your input in the comments helps us understand how this affects you and what you're hoping to accomplish with Bitbucket Server.

            As we've made a number of improvements to Bitbucket Server to help support a GitFlow model, including the branching model, automatic branch merges and branch permissions, we've decided to close this issue for now. If you have a specific suggestion related to GitFlow support, please raise a new issue outlining the specific feature and your use case that requires it.

            Product feedback is collected from a number of different sources and is evaluated when planning the product roadmap. You can learn more about our process here.

            Norman Ma

            Product Manager - Bitbucket Server

            Norman Ma (Inactive) added a comment - Hi everyone, Thanks to everyone for voting and commenting on this suggestion. Your input in the comments helps us understand how this affects you and what you're hoping to accomplish with Bitbucket Server. As we've made a number of improvements to Bitbucket Server to help support a GitFlow model, including the branching model, automatic branch merges and branch permissions, we've decided to close this issue for now. If you have a specific suggestion related to GitFlow support, please raise a new issue outlining the specific feature and your use case that requires it. Product feedback is collected from a number of different sources and is evaluated when planning the product roadmap. You can learn more about our process here . Norman Ma Product Manager - Bitbucket Server
            Norman Ma (Inactive) made changes -
            Remote Link New: This issue links to "Page (Extranet)" [ 190337 ]

            mbneto1559721656, yes you can set up a branch model with automatic merges for this. For details, see our documentation

            Roger Barnes (Inactive) added a comment - mbneto1559721656 , yes you can set up a branch model with automatic merges for this. For details, see our documentation

            Hi, I was hoping I could use the gitflow model with stash without having to manually merge hotfixes and release branches back to develop. Is there any way to do this from stash?

            Mario Bittencourt added a comment - Hi, I was hoping I could use the gitflow model with stash without having to manually merge hotfixes and release branches back to develop. Is there any way to do this from stash?

            From STASH-5525, a use case to consider:
            "Stash supports a variety of branching models, gitflow being one of them. In gitflow a release branch is a short lived staging branch for a yet to be released version. In this situation it may make sense to merge production into the release branch automatically after merging a hotfix into production.
            Users currently have to merge hotfix changes from production to their release branch(es) as a separate action."

            Roger Barnes (Inactive) added a comment - From STASH-5525 , a use case to consider: "Stash supports a variety of branching models, gitflow being one of them. In gitflow a release branch is a short lived staging branch for a yet to be released version. In this situation it may make sense to merge production into the release branch automatically after merging a hotfix into production. Users currently have to merge hotfix changes from production to their release branch(es) as a separate action."
            Roger Barnes (Inactive) made changes -
            Link New: This issue incorporates STASH-5525 [ STASH-5525 ]

              Unassigned Unassigned
              4bb57f013684 Ali
              Votes:
              86 Vote for this issue
              Watchers:
              68 Start watching this issue

                Created:
                Updated:
                Resolved: