---
schema_version: "1"
id: 36a03d3f22c06166904c5c40c30aea759c0beafffba308a6c4a4d8630a5788d2
title: Commit Changes to the Source Control Repository
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/devops_center_work_item_commit_changes.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.devops_center_work_item_commit_changes.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 2a8a7bfad8d3adc0faa81b2454133e3505c2cd66a8559133736bf630c439df39
description: After you decide which changes to include for the work item, commit the changes to the project’s source control repository. When you commit changes, they’re stored in the repository branch that was created when the work item moved to the In Progress stage.
products:
  - Salesforce Platform
release: "264"
---
# Commit Changes to the Source Control Repository

After you decide which changes to include for the work item, commit the changes to the project’s source control repository. When you commit changes, they’re stored in the repository branch that was created when the work item moved to the In Progress stage.

Before you can commit changes, you must [pull changes from the development environment](https://help.salesforce.com/s/articleView?id=platform.devops_center_work_item_pull_changes.htm&release=264.0.0&type=5 "Because the development environment has source tracking enabled, DevOps Center knows what files have been added, changed, or removed. When you pull changes, DevOps Center displays a list of all files that it has identified as changed. These changes aren’t associated with the work item until you select and commit them to the source control repository.") (1).

1. In the work item Changes tab, select the changes to commit (2).
    
    Only the changes you select and commit become part of the work item. Unselected changes are available to commit in another work item.
    
    ![Select the changes to commit, then add a commit comment.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-devops_center-264-0-0-production-enus/166010c3-4c34-4087-92ad-aea917baf524/devops_center/images/work-item-changes-select.png)
2. (Optional) Add metadata components manually.
3. Add a commit comment. (3)
    
    Include what’s distinctive about the changes, so you can identify an individual commit by more than just its timestamp. A single work item can have multiple commits. You can continue to work in your development environment and commit a new group of changes for the same work item.
4. Click **Commit Changes** (4).
    
    The changes are committed to the work item’s project repository branch.
    
    The branch is named after the work item, so it’s clear where the changes it contains came from. For example, the branch for a work item WI-000002 looks something like:
    
    ```
    https://github.com/<username>/<repo-name>/tree/WI-000002
    ```
    
    ```
    https://bitbucket.org/<workspace>/<repo-name>/branch/WI-000002
    ```
    
    After you commit changes to the repository, the source tracking for these components in your development environment is reset. This reset ensures that changes that are already committed don’t keep showing up when you pull changes from the development environment.
5. (Optional) To see the branch in the source control repository, click the Source Control Branch URL.
    
    The Code page for the branch is shown. Explore the changes you recently committed in the source control repository.

If you see the error `Ending position out of bounds: -1`, ask a Salesforce admin to turn off high assurance for authorization providers. See [Troubleshoot DevOps Center Errors](https://help.salesforce.com/s/articleView?id=platform.devops_center_troubleshooting.htm&release=264.0.0&type=5 "Here are some tips if you encounter issues while using DevOps Center. If needed, get help from your team manager or Salesforce admin to resolve these issues.") for details.

- **[Stalled Commits](https://help.salesforce.com/s/articleView?id=platform.devops_center_commit_stalled.htm&release=264.0.0&type=5)**  
    A stalled commit can occur when the updates from the external services back to DevOps Center are interrupted during the commit operation. After you determine when the failure occurred, you can fix it.