Azure-devops-docs: Clarification needed

[ctahok]

The article says: "All users will be allowed to create branches under the features/ and users/ folders."
Then in issued commands, it specifies /branch:features & /branch:users which are not folders but branch names.
So when those folders are being created?
After completing all above commands I am only able to create branches called feature, users, releases and nothing else. Even after creating users folder I am not able to create any branches undernith with error: "Failed to create branch users/nb from master with error: VS403660. You do not have permission to create ref refs/heads/users/nb. Please ensure the ref naming convention being used is allowed in this...."

Please help.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 330532da-d568-b010-a154-62afb1844e4a
• Version Independent ID: 4efad37d-4ec2-033e-51b1-b9f588e675c6
• Content: Require branches to be created in folders - Azure Repos
• Content Source: docs/repos/git/require-branch-folders.md
• Product: devops
• Technology: devops-code-git
• GitHub Login: @apawast
• Microsoft Alias: sdanie

[WilliamAntonRohm]

@ctahok -- thanks for your question. Here are a couple of options where you might consider asking your question:

• Azure DevOps on Stack Overflow

• Azure DevOps Support Bot

  @apawast -- please look into potential documentation impact.

[aivsim]

Explanation provided in the docs says: "Then, allow contributors to create branches under features and users."

Commands bellow that text only allow to create branches specifically named features and users, but not anything like features/add-button or users/tom/add-readme.

[ctahok]

Why not to make creation folders easier? My users are doing it anyway via GitHub itself.
See it at https://i.imgur.com/LkbzNtc.png

[aivsim]

@ctahok All I'm trying to say that provided command only allow to create one specific branch.
I need to create a policy that I would be able to create any branch with this naming convention: features/<my-branch-name>