Before merging a branch, it is a best practice to determine your answers to the following questions:
A best practice is to lock the branch rulesets after development is complete.
To resolve conflicts, you must unlock the branch ruleset. You can unlock branch rulesets only if there are conflicts. After you resolve conflicts, try merging branch rulesets again.
A best practice is to always create a new ruleset version in the base ruleset to contain the rules from the corresponding branch ruleset, because doing so makes it easy to deliver enhancements in a precise, modular way.
A best practice is to lock the new ruleset version in the base ruleset, because in the multi-team environment that typically uses branches, locking the ruleset version alerts other teams that the features in that version are complete as of the point in time the version was created.
If the Merge Branches wizard encounters checked-out rules in the branch rulesets to be merged, it displays a warning and provides a report of the checked-out rules. All rules must be checked in before you can complete the merge. If you exit the wizard to complete steps to check in the rules, you must restart the Merge Branch RuleSets wizard.