How can we improve Azure DevOps?

Allow for gitflow branching model

This suggestion is migrated to Developer Community. Please use below link to view the current status.
https://developercommunity.visualstudio.com/content/idea/365447/allow-for-gitflow-branching-model.html
We would like to allow for a git flow model. Or a simple branching model with branch permissions such that only team leads are capable of merge (after code review) and developers may only check into their feature/issue branch.

http://nvie.com/posts/a-successful-git-branching-model/

71 votes
Sign in
(thinking…)
Password icon
Signed in as (Sign out)

We’ll send you updates on this idea

Anonymous shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

6 comments

Sign in
(thinking…)
Password icon
Signed in as (Sign out)
Submitting...
  • DanC commented  ·   ·  Flag as inappropriate

    Hello - when is this bit coming into VSTS:

    "setting policies on branch paths like releases/ or features/"

    Currently we have a manual setup fo reach feature branch policy to follow gitflow and PR/Auto build which woudl be greatly enhanced if we coudl add the policies at "path" level :-)

    Also, abilyt to add branch templates would be good.
    That way we could create gitflow templates, including policies, for feature/release/hotfix.

  • Sławek commented  ·   ·  Flag as inappropriate

    After using gitflow with tfs my current issue is finishing release/hotfix. I do that on my machine but at the end I have changes in develop and master that I have to push to the server. And that cause problem because I've policies that prevent me from direct push (without PR). It would be nice to have to tool to finish release/hotfix on server side that can somehow bypass this policy like PR.

Feedback and Knowledge Base