---
schema_version: "1"
id: 8759c97ec4c92d4b9a5d82ec858b72f95ef9cc86327ef9c59671ca9572ce64f9
title: Review and Resolve Conflicts in Your Source Control
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/devops_center_promotion_resolve_conflicts_github.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.devops_center_promotion_resolve_conflicts_github.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 90eedb8e1adac5f7a21707e2fc2143ea6ebf9d747c13bdbe7cf650f80a0e9085
description: In cases where DevOps Center can’t combine work items or you choose not to combine, DevOps Center blocks the promotion. In this case, you manually edit the files directly in your source control to resolve the conflict in the affected branch.
products:
  - Salesforce Platform
release: "264"
---
# Review and Resolve Conflicts in Your Source Control

In cases where DevOps Center can’t combine work items or you choose not to combine, DevOps Center blocks the promotion. In this case, you manually edit the files directly in your source control to resolve the conflict in the affected branch.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Lightning Experience in <strong>Professional</strong> (API access required), <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions</td></tr></tbody><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Government Cloud Plus</strong> as interoperable. Turning on DevOps Center in Government Cloud Plus orgs can send data outside the authorization boundary. Contact your Salesforce account executive for more details.</td></tr></tbody><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Not available in: <strong>EU Operating</strong> Zone. EU Operating zone is a special paid offering that provides an enhanced level of data residency commitment. DevOps Center <em>is</em> supported in orgs in the EU that aren’t part of EU OZ, per standard product terms and conditions.</td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d10505e101">User Permissions Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d10505e101 ">To resolve merge conflict in source control: </td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d10505e101 ">DevOps Center Deployment Manager</td>

          </tr>
        </tbody>
      </table>

These steps apply to GitHub. To resolve merge conflicts manually in Bitbucket, see [Resolve merge conflicts](https://support.atlassian.com/bitbucket-cloud/docs/resolve-merge-conflicts).

1. From the work item dropdown (on the stage or work item you’re promoting from), select **View Change Request** to go into GitHub to view the pull request and see the merge conflicts.
    
    Repeat these steps for all work items where the promotion failed.
    
    ![Pipeline Stages work item menu with View Change Request selected.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-devops_center-264-0-0-production-enus/166010c3-4c34-4087-92ad-aea917baf524/devops_center/images/pipeline-promotion-failed-view-pr.png)
2. In GitHub, click **Resolve Conflicts**.
    
    ![GitHub pull request that indicates that the branch has conflicts that must be resolved.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-devops_center-264-0-0-production-enus/166010c3-4c34-4087-92ad-aea917baf524/devops_center/images/pr-conflict-detected.png)
    
    In our example scenario, GitHub has identified one conflict (1) in one file, the Job Position Layout (2). If GitHub detects multiple conflicts in a file, you can use the Prev and Next links (3) to address each conflict one-by-one.
    
    ![Resolve conflict dialog in GitHub.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-devops_center-264-0-0-production-enus/166010c3-4c34-4087-92ad-aea917baf524/devops_center/images/pr-resolve-conflicts.png)
    
    The format of the conflict as shown in GitHub is:
    
    ```
    <<<<<<<<<< <branch 1 name>
    <code in branch 1>
    ==========
    <code in branch 2>
    >>>>>>>>>> <branch 2 name>
    ```
    
    In this example, the work item you attempted to promote (4) in branch WI-000006 is introducing a new field, while the CRM Integration branch doesn’t contain that new field. Also, the CRM Integration branch contains a field that the work item branch doesn’t contain (5), which was likely introduced by a different work item. In this case, you want to keep both these new fields, so you modify the file to eliminate the conflict.
    
    The [Metadata API Developer Guide](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_types_list.htm) provides the schema for each metadata type to assist you with editing the files directly. In this case, we can look at “Layout” in the guide to view the schema for <layoutItems>.
    
    The resulting changes now look like this:
    
    ```
    <layoutItems>
    <behavior>Edit</behavior>
           <field>Manager_Email__c</field>
    </layoutItems>
    <layoutItems>
    <behavior>Edit</behavior>
           <field>Department__c</field>
    </layoutItems>
    ```
3. At the top of the file, click **Mark as Resolved**.
4. Continue until you resolve all conflicts in the listed files.
5. Click **Commit Merge**, which saves your changes in the work item branch, W-000006.
    
    Notice that the conflicts are now resolved.
    
    ![GitHub pull request showing that the branch no longer contains any conflicts.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-devops_center-264-0-0-production-enus/166010c3-4c34-4087-92ad-aea917baf524/devops_center/images/pr-conflicts-resolved.png)
6. Return to DevOps Center to promote the work item, which merges the branch with the branch in the next stage, in this case, Integration.
7. In DevOps Center, promote the work items again.
    
    Alternatively, you can merge the change request in GitHub, then complete the promotion in DevOps Center or by using Salesforce CLI.

After you resolve conflicts, your development environments are out of sync with downstream pipeline environments, so we recommend that you synchronize your dev environment.