> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/arm-1/arm-features/version-control/ez-merge/create-pull-request-on-merged-changes-in-ez-merge.md).

# Create Pull Request on Merged Changes in ez-Merge

### Overview

The **Create Pull Request On Merged Changes** option allows users to create a Pull Request for merged changes instead of committing them directly to the destination branch.

ARM creates a temporary branch, applies and validates the selected changes, and then creates a Pull Request against the destination branch for external code review.

### Prerequisites

* Available in the **New UI**.
* **Pre-validation Merge** must be configured.
* Repository must support Pull Requests.
* Valid destination branch credentials must be configured under **My Profile**.

### Using Create Pull Request On Merged Changes

Navigate to **Version Control → ez-Merge** and select the required source and destination branches.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FlHMUrVJCBsiwUtrlaohM%2Fimage.png?alt=media&amp;token=1cd243e5-e2da-4954-bd7e-6b850c0ce154" alt=""><figcaption></figcaption></figure>

Select the required Merge Type Such as Single Revision, Entire Branch,Commit Label, Release Label, ALM Label.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FkVaJLHQIEkuSK0oJ93zk%2Fimage.png?alt=media&amp;token=c87b7616-aaff-4537-b214-481078f735e4" alt=""><figcaption></figcaption></figure>

Configure **Pre-validation Merge** and the required validation options, such as:

* File Diff
* Static Code Analysis
* Validate Deploy

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FebaskCwJUJ3nBbdAJomt%2Fimage.png?alt=media&amp;token=cd49f49e-b19c-4c7b-b3a7-0ca17a94ed47" alt=""><figcaption></figcaption></figure>

Enable **Create Pull Request On Merged Changes**.

When enabled, ARM creates a Pull Request instead of directly committing the merged changes to the destination branch.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FHMMQ2Z9yQCCiWtzK05o0%2Fimage.png?alt=media&amp;token=46039cde-1821-4c7b-96dd-3720f95cce7d" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FTcd0EwyoecWxbzs3oXqX%2Fimage.png?alt=media&amp;token=fcfb7010-730d-4942-8889-e4dae5dc06ed" alt=""><figcaption></figcaption></figure>

The following options are not applicable to this flow:

* Create commit label
* Create GIT tag
* Delete source branch
* Approvers / reviewers selection

Review the configuration and click **Create Pull Request**.

ARM will:

1. Create a temporary branch from the destination branch.
2. Apply the selected revisions to the temporary branch.
3. Run the configured merge validations.
4. Create a Pull Request from the temporary branch to the selected destination branch.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FWDT04cpelQEkfutTr4Hy%2Fimage.png?alt=media&amp;token=650ef70c-0597-45ea-a3fa-fda9313b744f" alt=""><figcaption></figcaption></figure>

### Process Logs

A new **Pull Request Creation** process log provides:

* Temporary branch creation details
* Pull Request creation details
* Pull Request URL

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FBEYEOmh4Wzg81KQBjVb4%2Fimage.png?alt=media&amp;token=76dcd1b1-38f8-4902-940e-e398f488ff79" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F1m3DqV0bqR1ub2j91KLk%2Fimage.png?alt=media&amp;token=3e38699a-5ff9-4524-a1ec-a0c692b3b16a" alt=""><figcaption></figcaption></figure>

The **Commit** and **Post Merge Updates** process logs are not available for this flow because ARM does not directly commit changes to the destination branch.

### Review and Merge

Once the Pull Request is created, use the URL available in the process log to open it in the external repository.

The Pull Request can then go through the repository's standard review process, including external or AI-based code review.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F1QnJvQ7IH8p6ef0bfMMs%2Fimage.png?alt=media&amp;token=5a5d31f8-2472-40c3-ace9-15a954ad0340" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FPwnYykiWXQkK0DA5tLSL%2Fimage.png?alt=media&amp;token=68c3ef6e-0f56-4935-acd2-6506a18c0983" alt=""><figcaption></figcaption></figure>

The final merge can be completed through:

* **External Pull Requests History** in ARM, or
* The external Git repository.

### Expected Result

The selected revisions are applied to a temporary branch, validated, and a Pull Request is created against the destination branch. The destination branch remains unchanged until the Pull Request is reviewed and merged.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://knowledgebase.autorabit.com/product-guides/arm-1/arm-features/version-control/ez-merge/create-pull-request-on-merged-changes-in-ez-merge.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.