> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gorules.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Change Requests

> Review and approve changes before merging into the main branch.

Change requests (CRs) provide a review workflow for merging branch changes into main. They're similar to pull requests in Git, enabling team collaboration and approval processes.

## Change request list

The Requests page shows pending and completed change requests:

### Tabs

| Tab     | Contents                               |
| ------- | -------------------------------------- |
| Pending | Open requests awaiting review or merge |
| Closed  | Completed or cancelled requests        |

### List columns

| Column | Description                           |
| ------ | ------------------------------------- |
| Name   | Request title (usually merge message) |
| Type   | Action type (merge, deploy, etc.)     |

## Creating a change request

1. Open your branch in the editor
2. Click "Merge"
3. Check "Open change request"
4. Enter a descriptive message
5. Click "Open change request"

The request appears in the Pending tab and is linked from the branch.

## Change request detail

Each request shows:

### Overview tab

**Details section:**

* Copy test URL - Get a URL to test this version
* Branch - Source branch being merged
* Action - What will happen (merge branch)

**Activity timeline:**

* Creation event with description
* Approval events
* Completion or cancellation

**Approval groups:**

* Required groups based on branch protection rules
* Shows requirement status (None, Single, Group)

**Actions:**

* Merge - Complete the request
* Cancel request - Abandon the changes

**Approvals:**

* List of users who approved
* Shows "No approves" if none yet

### Changes tab

Browse the files that will be modified:

* Visual diff of changes
* Click files to view details

## Review workflow

### With no approval required

1. Review the changes
2. Click "Merge"
3. Optionally add a comment
4. Click "Merge" to complete

### With approval required

1. Designated approvers review the changes
2. Approvers click to approve
3. Once requirements are met, merge becomes available
4. Click "Merge" to complete

<Note>
  Users cannot approve their own change requests. This ensures independent review.
</Note>

## Request states

| State          | Description                         |
| -------------- | ----------------------------------- |
| Pending Review | Awaiting review or approval         |
| Ready          | All requirements met, can be merged |
| Completed      | Successfully merged                 |
| Cancelled      | Request was abandoned               |

## Branch protection integration

Change requests work with branch protection rules:

| Protection mode | Behavior                                      |
| --------------- | --------------------------------------------- |
| None            | Direct merge, no CR required                  |
| Open Request    | CR created for visibility, no approval needed |
| Single Approval | One user must approve before merge            |
| Group Approval  | One member from each group must approve       |

## Completing a request

1. Click "Merge" on a ready request
2. Optionally add a completion comment
3. Click "Merge" to finalize

The branch changes are merged into main, and the request moves to Closed.