Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Understanding the merge subresource

Updated on April 5, 2022

Use the merge subresource to perform additional tests on conflicts, and then perform a merge operation.

This subresource takes the following parameters:

  • Request – http://serverURL/prweb/api/v1/branches/{id}/merge
  • Parameter – ID. The name of the branch that you want to merge. This parameter is required.
  • Response – The merge subresource returns a unique ID after a validation event occurs. During the merge, the status is saved to an instance of the System-Queue-Merge class.

To verify the status of a merge, use the Merges REST service, using the ID returned by the response.

You can also use the Queue Management landing page to view information about and remove merge requests without needing to know the response ID. Open the landing page by clicking Dev StudioSystemOperationsQueue Management.

You can also update logging levels to INFO on the pzMergeServicePostActionProcessing activity to log informational messages. These messages could provide information about why exceptions are occurring and also act as a reference that you can use if you are working with Pegasystems Global Customer Support. For more information about logging levels, see Logging Level Settings tool.

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us