For example, by using branches, two teams can work simultaneously on different application features, such as case type creation and notifications. Each team can make can make changes that do not affect the changes of the other team during the development process, even if the features use the same base rulesets. When the development process is complete, you can review branches to resolve any conflicts, and then merge the results into a target ruleset in order to make the new features available in the final version of your application.
To learn more about branched application development, see the following articles:
- Branches and branch rulesets
Branches help you manage work in development environments in which multiple teams contribute to a single application. You use branches to develop software simultaneously in a version-controlled environment. For example, a team can develop a feature in one branch while another team develops another feature in a different branch, even if the teams share the same rulesets.
- 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.