Project113

Creating Change Requests

A change request proposes merging changes from a source branch into a target branch. It is the central collaboration mechanism for code review.

Creating a CR

  1. Navigate to your repository and click the Changes tab.
  2. Click New Change Request.
  3. Select the source branch (your feature branch) and target branch (e.g., master).
  4. Enter a title and optional description.
  5. Configure merge settings if needed (strategy, auto-merge, etc.).
  6. Click Create.

CR States

Change requests go through several states:

  • Draft — Not ready for review yet. Can be edited freely.
  • Open — Ready for review and approval.
  • Locked — Discussion is locked.
  • Merged — Changes have been merged into the target branch.
  • Closed — The change request was closed without merging.
  • Stale — The target branch has moved ahead; needs rebasing or updating.

Draft Mode

Check the Create as Draft option to create the change request in draft state. Drafts are not ready for review and can be edited freely. When ready, transition the CR to Open to start the review process.

Dependencies

You can link your change request to existing CRs as dependencies. If your changes depend on another CR being merged first, expand the Dependencies section and select the relevant CRs. When creating a dependency, you can optionally choose to squash with a single dependency, which tries to combines both changes into one commit on merge.

Auto-Assigned Reviewers

If reviewer policies are configured, reviewers are automatically assigned when the CR is created based on the changed files, branch patterns, or title patterns.