Source control integration in ServiceNow Studio

  • Release version: Australia
  • Updated May 7, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Source control integration in ServiceNow Studio

    ServiceNow Studio enables you to link scoped or global applications on a non-production instance to a Git source control repository. This integration helps application developers collaboratively save, manage, and share multiple versions of an application directly within ServiceNow Studio. It supports importing, committing, pulling changes, creating tags, and branching, all essential for effective application lifecycle management.

    Show full answer Show less

    Integration Requirements

    • User must have the admin role.
    • The non-production instance requires network access to the Git repository.
    • Each application must be linked to its own Git repository.
    • Repository credentials must provide both read and write access, shared among all developers on the instance.

    Key Features in ServiceNow Studio

    • Edit Git repository credentials and connection details.
    • Commit all local application changes to the Git repository.
    • Apply remote changes from the Git repository to the instance.
    • Create and switch between branches to maintain multiple application versions.
    • Import applications directly from a remote Git repository.

    Note: Source control integration is supported only on non-production instances. For production instances, use the application repository, update sets, or ServiceNow Studio for managing applications.

    Working with Git Repositories Outside ServiceNow Studio

    The ServiceNow AI Platform provides limited support for modifying linked application files outside the instance, allowing developers to:

    • Move application files within the Git directory structure by configuring the snsourcecontrol.properties file.
    • Edit application files externally from ServiceNow Studio.

    The integration uses a checksum.txt file to detect external changes and trigger validation and sanitization processes, including:

    • Logging sanitization actions.
    • Removing unsupported files or folders.
    • Aborting operations if system files fail XML schema validation.
    • Skipping operations if non-system files fail validation.

    Only content within the specified application path is sanitized; other repository content is ignored.

    Connecting through a MID Server

    Using an existing MID Server allows connection to Git repositories behind firewalls, enabling secure access to source control repositories that are not directly accessible from the ServiceNow instance.

    Role and Permissions

    Admin role is required to link applications to source control, and repository credentials are shared among all application developers. For detailed collaboration and role management, refer to Application collaboration documentation.

    Managing Git Repository Configurations

    Within ServiceNow Studio, you can update repository configurations such as network protocols and credentials to maintain seamless connectivity and security for source control operations.

    Link your application to a Git source control repository in ServiceNow Studio to save, manage, and share multiple versions of a global or scoped application from a non-production instance.

    Linking an application to source control enables all application developers on a non-production instance to:
    • Import applications from a Git repository.
    • Pull and apply remote changes from a Git repository.
    • Commit all local changes on the instance to a Git repository.
    • Create tags to permanently link to a specific version of an application.
    • Create branches to maintain multiple versions of an application at the same time.

    What are the integration requirements?

    To link an application to source control:
    • The user must have the admin role.
    • The non-production instance must have network access to the Git repository.
    • Each application must be in its own Git repository.
    • The repository user credentials must grant read and write access.
    Note:
    All application developers on the instance share a single set of credentials per repository.

    What can you do with source control in ServiceNow Studio?

    After linking an application to source control, application developers can use ServiceNow Studio to manage the repository. From ServiceNow Studio, developers can:
    • Edit the application repository credentials.
    • Commit all local changes on the instance.
    • Apply remote changes from the repository.
    • Create a branch.
    • Switch branches.
    • Import an application from a remote repository.

    Source control integration does not support managing applications on a production instance. To manage applications on a production instance, use the application repository, an update set, or ServiceNow Studio. For more information, see Application sharing.

    What can you do with source control from a Git repository?

    The ServiceNow AI Platform offers limited support for modifying linked application files outside of an instance. From Git, developers can:
    • Move application files to a different Git directory structure.
    • Edit application files outside of ServiceNow Studio.

    The system generates a properties text file called sn_source_control.properties at the root level of the repository. To move application files to a different Git directory structure, set the path parameter to specify the subfolder path containing the application files. For example, to move your application to the src/app subfolder, set the path to path=src/app.

    The system generates a checksum.txt file in the Git repository to determine if any application files have been changed outside of ServiceNow Studio. When the checksum value from the file matches the current checksum value, the integration skips the validation and sanitization process. When the checksum values do not match, the integration validates and sanitizes the application files as part of the source control operation. The sanitization process:
    • Creates upgrade log entries for each sanitization action taken.
    • Removes unsupported folders and files from the repository.
    • Aborts all source control operations when a system application file fails XML schema validation. For example, if a database dictionary record fails XML schema validation, the system aborts all operations.
    • Skips the current source control operation when a non-system application file fails XML schema validation.

    The Git integration sanitizes only content within the application path listed in the sn_source_control.properties file. Repository content outside the application path is ignored.

    How do I connect through a MID Server?

    Use an existing MID Server to connect to a source control repository. Connecting an application through a MID Server enables access to repositories behind a firewall.

    Source control role permissions

    For more information about roles and collaborators, see Application collaboration.