Table of Contents

Branches and branch rulesets


Only available versions of this content are shown in the dropdown

Typically, you use branches in development environments in which multiple teams contribute to a single application. You use branches to develop software in parallel in a version-controlled environment. For example, your teams can develop one feature in a branch while another team develops a feature in a different branch, even if they share the same base rulesets.

After you create branches and create rules in them, you can work with branches in a number of ways. For example, you can create reviews for branches to ensure that they are guardrail-compliant. Also, after feature development is complete, you can merge the changes you made for all features into the base ruleset.

  • Implementing branched application development

    For faster delivery of your products, configure your application development to use branches. By implementing branches, team members can work simultaneously on multiple features, without the risk of interrupting work of different team members.

  • Branch operations

    After you create branches and develop rules in branch rulesets, you can work with branches in a number of ways. For example, you can create branch reviews with other users, delete branches form the system, and lock branches before you merge them.

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.