Uploaded image for project: 'Bitbucket Cloud'
  1. Bitbucket Cloud
  2. BCLOUD-17710

Gitflow Workflow unable to merge hotfix/ and/or release/ pull-request to both master and develop

    XMLWordPrintable

Details

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      A problem I am facing and a problem I am seeing others face is the inability for a 'hotfix/' branch to be merged to master and develop branches. I have seen many an unanswered StackOverflow question about this same issue.

      Many companies, including my own, use the git-flow or GitFlow WorkFlow (Atlassian Documentation). This requires that a hotfix is created based on the master branch and be merged back into the master and develop branch.

      Atlassian documentation on the matter alludes that this feature exists. See, Making a Pull Request - Tutorial, specifically the section titled: "Gitflow Workflow With Pull Requests". It describes exactly, and correctly, how the workflow should work. I can not find this feature anywhere in bitbucket.

      If it exists and I can not find the feature - I apologize, please point me in the right direction.

      Otherwise, a more succinct version of my request is:

      • When a branch is prefixed with either of the following prefixes it should be merged to master and then develop branch.
        • hotfix/
        • release/
      • Should only happen if you have the branching workflow enabled for your repository

      Please feel free to reach out to me with any other questions.

      Attachments

        Activity

          People

            Unassigned Unassigned
            49a4fe705f44 robertg-ld
            Votes:
            24 Vote for this issue
            Watchers:
            18 Start watching this issue

            Dates

              Created:
              Updated: