Table of Contents

Branches and branch rulesets

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.

  • Configuring an application to use branches and branch rulesets

    To use branches in your application, you create a development application that is built on your production application. You create rules and save them in your development application, creating branch rulesets. You can then work with branches in a number of ways, such as creating branch reviews and merging branches.

  • 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.

  • Adding branches to your application

    You can create branches in your development application, add a branch that exists in a system, or add a branch from a repository that is configured on a remote development system.

Suggest Edit

0% found this useful

Have a question? Get answers now.

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