---
sourceDocument: Yokohama Build or modify applications
sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/application-development

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Commit changes to a repository

# Commit changes to a repository {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Commit changes made in your application in App Engine Studio (AES) to a linked Git repository. You can either select a few changes to commit, or commit all changes on the instance at once.

## Before you begin

* Role required: admin
* [Link an application or application-customization to source control](https://www.servicenow.com/docs/BpAz~yi7BVoU982heALpUA "Linking an application or application-customization to source control allows application developers to manage changes in App Engine Studio (AES) from a Git repository.")
{#source-control-commit-changes__ul_zyd_vlt_s5}

## Procedure

1. Navigate to AllApp EngineApp Engine Studio.
2. From the My Apps page, open your application.
3. Select Source controlCommit changes.  
   The system displays the Select files to commit to source control window. The file changes from all the updates sets display. By default, the file changes from the current update set display.
4. Select the file changes you wish to commit.
5. To include untracked changes, select the Include changes not tracked via the Customer Update \[sys_update_xml\] table check box.  
   * The default for this check box is set via the glide.sourcecontrol.default_commit_mode property.
     * Property can be set to include_untracked or exclude_untracked.
     * The include_untracked mode commits the updates to the application that do not generate sys_update_xml records, as well as any user-selected updates.
     * The exclude_untracked mode commits only updates selected by the user in the Select files to commit to source control dialog.
     {#source-control-commit-changes__ul_x41_fhl_spb}
   * The base system setting for the property is exclude_untracked.
   * To hide the check box and use the value of the glide.sourcecontrol.default_commit_mode property, create the sn_devstudio.vcs.allow_commit_mode_selection property and set it to false.
   * Checking this check box may incur a performance penalty.

   {#source-control-commit-changes__ul_up1_qgl_spb}  
   Note:  
   Commits always occur in include_untracked mode in
   the following cases:
   * Linking to source control for the first time. (To learn more, see [Link an application or application-customization to source control](https://www.servicenow.com/docs/BpAz~yi7BVoU982heALpUA "Linking an application or application-customization to source control allows application developers to manage changes in App Engine Studio (AES) from a Git repository.").)
   * Publishing an application that's linked to source control from App Engine Studio.
   * Selective commit mode is disabled.
   {#source-control-commit-changes__ul_fzw_4hl_spb}
6. Select Continue.
7. In Commit comment, enter a comment for the changes.
8. Select Commit Files.  
   The following operations occur:
   * The system identifies all local changes.
   * The system commits all local changes to the remote repository.

   {#source-control-commit-changes__ul_ilx_545_s5}  
   Note:  
   For list of known files that don't have customer update records and are untracked, see [Customer Updates table](https://www.servicenow.com/docs/access?context=r_CustomerUpdatesTable&version=yokohama&pubname=yokohama-platform-security&ft:locale=en-US).
{#source-control-commit-changes__steps_lt3_bp5_s5}

*[\>]: and then