---
sourceDocument: Australia Build or modify applications
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/application-development

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Commit changes

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

Release version: Australia  
Updated May 27, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Commit changes made in ServiceNow Studio to a linked Git repository by selecting individual file changes or committing all changes on the instance at once.

## Before you begin

[Link an app to source control in ServiceNow Studio](https://servicenow-prod.fluidtopics.net/DawPgaSCzbztW8HaLVSwAg "Link an application or application customization to a Git repository in ServiceNow Studio so application developers can manage changes directly from the platform.")

Role required: admin

## Procedure

1. Navigate to AllApp EngineServiceNow Studio.
2. In the file navigator, select the application you want to open.
3. Select App details to open the app in the canvas.
4. Select Source controlCommit changes.  
   File changes from all update sets display. By default, changes from the current update set display first.
5. Select the file changes to commit.  
6. 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.
     * The property can be set to include_untracked or exclude_untracked.
     * The include_untracked mode commits 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 modal.
     {#sns-sc-commit-changes-to-repository__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.
   * Selecting this check box may incur a performance penalty.

   {#sns-sc-commit-changes-to-repository__ul_up1_qgl_spb}  
   Note:  
   Commits always occur in include_untracked mode in the following cases:
   * Linking to source control for the first time. For more information, see [Link an app to source control in ServiceNow Studio](https://servicenow-prod.fluidtopics.net/DawPgaSCzbztW8HaLVSwAg "Link an application or application customization to a Git repository in ServiceNow Studio so application developers can manage changes directly from the platform.").
   * Publishing an application linked to source control from ServiceNow Studio.
   * Disabling selective commit mode.
   {#sns-sc-commit-changes-to-repository__ul_fzw_4hl_spb}
7. Select Continue.
8. Enter a comment for the changes in the Commit comment field.
9. Select Commit Files.

## Result

The following operations occur:

* The ServiceNow AI Platform identifies all local changes.
* The ServiceNow AI Platform commits all local changes to the remote repository.

{#sns-sc-commit-changes-to-repository__ul_ilx_545_s5}  
Note:  
For list of known files that do not have customer update records and are untracked, see [Customer Updates table](https://www.servicenow.com/docs/access?context=r_CustomerUpdatesTable&version=australia&pubname=australia-platform-security&ft:locale=en-US).

*[\>]: and then