A pull request is a special type of review that you use to evaluate and merge a set of defined changes, typically in a topic stream.
Key Facts
Pull requests are a collaborative process that allows a team to:
Review the proposed code changes.
Add review comments and contribute to a discussion.
Catch problems early before they become costly to fix.
Protect your mainline stream from unwanted changes, bad merges, and broken builds.
Approve changes and merge them into a mainline.
Pull requests are related to two streams:
The source stream, where the pull request changes are made and reviewed, typically a topic stream.
The target stream, where the pull request changes will be merged to, typically a mainline.
Pull requests can be related to a request, which is used to merge the pull request changes. If the target stream has CM rules enabled, a request is required for the merge to succeed.
Pull requests have a single author and can be assigned to multiple lead and optional reviewers. When you publish a pull request, the reviewers are notified.
The related topic stream should preferably contain a small number of changesets. If there are too many changes, the pull request becomes too large to review effectively.
Pull requests enable you to merge changes automatically into a parent stream without involving a work area.
Pull requests can run Micro Focus Pulse chains. Chains helps you to decide if the changes in a stream are healthy. For information about Pulse see the online help.
Pulse administrators can configure a pull request to be automatically created when a topic stream is created. The new pull request is automatically linked to the topic stream. In Pulse go to:
Suites | <suite name | <CM product> | Settings | Pull Requests