--- sourceDocument: Brazil Build or modify applications sourceDocumentLink: https://www.servicenow.com/docs/r/application-development Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil Build or modify applications ft:clusterId : - cadev bundleId : - cadev workflow : - Development, Data, and Analytics --- # Use AES with a Git source control repository # Use AES with a Git source control repository {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) 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 Use AES with a Git source control repository App Engine Studio (AES) enables application developers to manage their application repositories through Git source control integration on non-production ServiceNow instances. After an administrator links an application to a Git repository, developers can import, pull, commit, branch, and tag application changes directly within AES to facilitate collaboration and version control. This integration does not support production instance application management, which requires alternative methods such as update sets or the application repository. Show full answer Show less ## Key Features * **Repository Management in AES:** Developers can edit repository credentials, commit local changes, apply remote changes, create and switch branches, and import applications from Git repositories using AES. * **Collaboration Control:** Only changes checked into Git are visible to other developers, ensuring controlled sharing and version consistency. * **Git Repository Operations:** Limited external modifications are supported, including moving application files within the Git directory and editing files outside AES, with a configuration file (`snsourcecontrol.properties`) to specify application file paths. * **Checksum and Sanitization:** The integration uses a `checksum.txt` file to detect external changes and performs validation and sanitization to maintain repository integrity. Unsupported files are removed, and schema validation failures can abort or skip operations to protect data quality. * **MID Server Support:** Existing MID Servers can be used to connect to Git repositories behind firewalls, enabling secure repository access. * **Source Control Operations in AES:** Developers can import apps, work with Git changes (pull, commit), create versions and branches, stash and apply changes later, resolve conflicts by selecting file versions, view commit histories, and reorganize application files within the Git repository. ## Key Outcomes * Streamlined application development workflow through integrated Git source control within AES on non-production instances. * Improved collaboration and version management by enabling developers to work concurrently on multiple versions and branches of applications. * Enhanced repository integrity and consistency by validating and sanitizing external file changes before applying them. * Flexibility to manage application files and related supporting content (e.g., automated tests) within the same Git repository for better organization. * Secure access to repositories behind firewalls facilitated by MID Server connectivity. App developers working in App Engine Studio (AES) can manage their data repository in numerous ways. After your [admin has linked an application to Source control](https://www.servicenow.com/docs/h4jlTogIujaJmQEDAaZ5ZA "Enable application developers to integrate App Engine Studio (AES) with a Git source control repository to save and manage multiple versions of an application from a non-production instance."), all application developers on a non-production instance can perform these actions: * 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 given version of an application. * Create branches to maintain multiple versions of an application simultaneously. {#aes-source-control-use__ul_f23_qsk_p5} Note: If you're using source control to collaborate with other developers, only changes that have been checked in are available to other developers. For example, if an admin creates a new flow for an app that's linked to Git, the new flow won't be available in the app for other AES users until the admin checks the flow into Git. ## Options available from App Engine Studio {#aes-source-control-use__section_k2d_kyg_kjb} After an application has been linked to source control, application developers can use App Engine Studio to manage the repository. From App Engine 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. {#aes-source-control-use__ul_u55_hl4_q5} Source control integration does not support managing applications on a production instance. Instead, you can manage applications on a production instance using the application repository, an update set, or App Engine Studio. For more information about managing applications on a production instance, see [Application sharing](https://www.servicenow.com/docs/5TCgBKajvLBy6~gs6G_Wmg "Administrators can share applications that are complete and are ready for use on other instances."). ## Options available from a Git repository {#aes-source-control-use__section_spn_nyg_kjb} The ServiceNow 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 App Engine Studio. {#aes-source-control-use__ul_gtn_34f_kjb} 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, application developers can set the path parameter to specify the subfolder path containing their application files. For example, if you moved 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 App Engine 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. {#aes-source-control-use__ul_sqt_z4f_kjb} The source control integration sanitizes only content within the application path listed in the sn_source_control.properties file. Repository content outside the application path is ignored. ## MID Server support {#aes-source-control-use__section_ew2_4y1_njb} Use an existing MID Server to connect to a source control repository. Accessing an application through a MID Server enables access to repositories behind a firewall. * **[Source control operations in App Engine Studio](https://www.servicenow.com/docs/3BaNQI1sOf8ZjjTxZivA_w)** The source control integration primarily supports operations from App Engine Studio (AES), but can also support some operations directly from the Git repository. * **[Import application or application-customization from source control](https://www.servicenow.com/docs/OB6B8QQnH1A4vqlwT07XHw)** Import an app or app customization from a source control repository into App Engine Studio (AES) to continue developing it on this instance. * **[Work with changes in Git](https://www.servicenow.com/docs/A2AQc2yuOyA00klfBSxI5A)** Developers using App Engine Studio (AES) can pull and commit changes in their Git repository. * **[Create versions and branches in Git](https://www.servicenow.com/docs/wjuF3tfKTvd8U642BftTqg#create-versions-branches-git)** App developers using App Engine Studio (AES) can create versions and branches in their Git repositories. * **[Stash changes](https://www.servicenow.com/docs/PpytZMsA2B3qMSGbm6_2EA)** Developers can remove and save changes locally to apply them later, and manage stashed changes from App Engine Studio (AES). * **[Resolve conflicts](https://www.servicenow.com/docs/oQiqgNhW1NU4vn7tzsqZ4A)** App developers can select the app file version to use when applying remote or stashed changes in App Engine Studio (AES). * **[View commit history](https://www.servicenow.com/docs/J_IaaZ4NqEHFeSwYufA5sA)** App developers can view the commit history of apps linked to a source control repository in App Engine Studio (AES). * **[Move application files in a Git repository](https://www.servicenow.com/docs/IRgp6X8CM9sqmxzA4Y0oQQ)** Move application files linked to source control to any folder of the repository when working in App Engine Studio (AES). Allow application developers to store supporting content such as automated tests in the same repository as the applications they support.