---
sourceDocument: Australia Build or modify applications
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/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


---

# Source control integration

# Source control and Developer Sandboxes {#ariaid-title1}

Release version: Australia  
Updated October 27, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Use source control with Developer Sandboxes to enable parallel development and help avoid merge conflicts.

## Source control overview {#dev-sandboxes-source-control__section_lk2_c5q_jgc}

Traditional, single-instance development is a model that requires ongoing oversight and maintenance. Sharing a single instance increases the risk of merge conflicts and restricts teams to a single version of code. Enterprise IT
architecture standards increasingly require full version control for architectural compliance and IP management.

In support, use Developer Sandboxes in tandem with Git source control to synchronize changes between the base and sandbox environments.

Using source control, developers can work on independent branches and merge them according to your organization's general guidelines.  
Figure 1. Example branching strategy with source control

## Git credentials {#dev-sandboxes-source-control__section_ebz_c5q_jgc}

Each sandbox inherits Git credentials from the base instance. However, developers can add or change Git credentials locally within the sandbox. A new branch should be created for each sandbox.

Sandboxes inherit Git credentials from the base instance.