Application developers can commit their changes on the instance to the linked Git repository. You can either select a few changes to commit, or commit all changes on the instance at once.

Before you begin

Procedure

  1. Navigate to All > Source Control > Commit 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.
    Select files to commit
  2. Select the file changes you wish to commit.
  3. 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.
    • The base system setting for the property is exclude_untracked.
    • Prior to the ServiceNow Rome release, only the include_untracked mode is used.

    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.

    Note:

    Commits always occur in include_untracked mode in the following cases:

  4. Click Continue.
  5. In Commit comment, enter a comment for the changes.
  6. Click Commit Files.
    The following operations occur:
    • The system identifies all local changes.
    • The system commits all local changes to the remote repository.
    Note: For list of known files that don’t have customer update records and are untracked, see Customer Updates table.