To increase the quality of your application, you can create reviews of branch contents to improve branch quality by, for example, ensuring that the rules are guardrail-compliant. You can assign branch reviews to other users, use Pulse to collaborate on reviews, and close reviews after you have addressed any issues.
If you have a Default email account configured, you are notified when reviews are assigned to you and when reviews are closed. For more information, see Creating an email account in Dev Studio.
If Pulse notifications are configured, you can receive emails when a new comment is added or when a reply is posted to a new comment. For more information, see Configuring Pulse email notifications.
You can override the following when rules to allow merges when branches are unlocked or not reviewed:
- pyAllowMergeWhenNotReviewed: Override to disallow merges when branches have not been reviewed.
- pyAllowMergeWhenUnlocked: Override to disallow merges when branches are not locked.
- Creating a branch review
You can create a review for a branch so that you and other review team members can collaborate to improve the branch quality before you merge the branch. Only one branch review can be open at a time.
- Modifying a branch review
For open branch reviews, you can modify the list of users who are assigned to the review.
- Deleting a branch review
You can delete both open and closed branch reviews.
- Closing a branch review
You can close a branch review after all comments have been addressed.
- Reopening a branch review
You can reopen a branch review after the review was closed, for example, if a reviewer inadvertently closed it.
- Reviewing branches
If you are a branch reviewer, you can open reviews and inspect the rules within the branch improve the quality of the branch, for example, before you merge its contents. You can also communicate with other users in Pulse to work collaboratively on branch reviews.
ArticleBranches and branch rulesets