Use pull requests to manage changes
This section provides information about pull requests, a special type of review that you use to evaluate and merge a set of defined changes, typically in a topic stream or branch.
Pull requests are a collaborative process that enables a team to:
- Review the proposed code changes.
- Add review comments and contribute to a discussion.
- Protect your mainline stream/branch from unwanted changes, bad merges, and broken builds.
- Approve changes and merge them into a mainline.
Pull request behavior:
- Pull requests are related to two streams or branches: the source stream/branch, where the pull request changes are made and reviewed, typically a topic stream; and the target stream/branch, 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 changes in the pull request.
- Pull requests enable you to merge changes into a target stream or branch without using a work area. For details, see Merge changes in pull requests.
- Pull requests can run chains to help you decide if the changes in a stream are healthy. For details, see Run chains on pull requests.
As an administrator, you can instruct PulseUno to create a pull request automatically when a branch or topic stream are created. The new pull request is automatically linked to the branch or topic stream. For details, see Configure how pull requests are created.
See also: