Merge branches to apply all of the changes made in the source branch to the target branch.
You can only merge committed branches.
If two branches each contain a Trust Framework or Test Suite definition that was created natively in that branch but has the same exact name and hierarchy in the other branch, the merge operation will not complete successfully.
This happens because the duplicated items don't come from the same source, making the branches ineligible for merge conflict resolution. Rename any such duplicated items in one branch before attempting to merge.
- Click Branch Manager.
- Click Version Control.
Select the source branch.
You can select top-level branches and subbranches.
- Click Set branch as Merge Source.
Go to the target branch and click Set branch as Merge
With the source and target branches selected, the Merge Branches button should appear.
Click Merge Branches.
The PingAuthorize Policy Editor checks for merge conflicts.
If no conflicts are found, the changes are merged from the source branch into the target branch. Your merge is complete, and you can skip the remaining step.
If conflicts are found, complete the following step to resolve the conflicts.
If an entity has changed in both the incoming and existing branches, the Policy Editor flags a conflict. You must resolve the conflict for the merge to continue. Conflicts appear in the Merge Conflicts table.
- If you need all or almost all of the sections from one branch, click either the Take All Incoming button or the Keep All Existing button.
To examine conflicts one at a time, click Resolve Individual
On the resulting screen, select the Show diff check box to highlight differences.
Decide which change to keep and click either Keep Existing or Take Incoming.
After you resolve all conflicts, close the entity difference box.
The Apply Merge button becomes available.
- Click Apply Merge.