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

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Source control in ServiceNow Studio

# Source control in ServiceNow Studio {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 min. de leitura

App developers working in ServiceNow Studio can manage their data repository in numerous ways using source control.  
After your admin has linked an app to source control, 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.
{#source-control-in-servicenow-studio__ul_f23_qsk_p5}

For more information, see [Link an app to source control in ServiceNow Studio](https://servicenow-prod.fluidtopics.net/AJB3RRVvlbN9W7aSTZbKvw "Linking an application or application-customization to source control allows application developers to manage changes in ServiceNow Studio from a Git repository.").  
Nota:  
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 users until the admin checks the flow into Git.
* **[Source control operations in ServiceNow Studio](https://servicenow-prod.fluidtopics.net/O1cPv3xDO13pNnutOgHy_g)**   
  The source control integration primarily supports operations from ServiceNow Studio, but can also support some operations directly from the Git repository.
* **[Import an app from source control in ServiceNow Studio](https://servicenow-prod.fluidtopics.net/D~TnCZ4Z~KCjpo3HxW9BhQ)**   
  Importing an application from source control results in a new application being created in your ServiceNow instance based on the remote repository you specify. The account credentials you supply must have read access to the remote repository, and the remote repository you specify must contain a valid ServiceNow application.
* **[Work with changes in Git](https://servicenow-prod.fluidtopics.net/FNA5biCdTV9ynTnDzNoRtw)**   
  Developers using ServiceNow Studio can pull and commit changes in their Git repository.
* **[Create versions and branches in Git](https://servicenow-prod.fluidtopics.net/zjFLgDBGP66_0JMzhyaNyA#sns-sc-create-versions-branches-git)**   
  App developers using ServiceNow Studio can create versions and branches in their Git repositories.
* **[View commit history](https://servicenow-prod.fluidtopics.net/otfcOlZtiEmKwCh1LGxVVg)**   
  View the commit history of apps linked to a source control repository in ServiceNow Studio
* **[Move application files in a Git repository](https://servicenow-prod.fluidtopics.net/K2sfXFq3hb_d9YKXIx7WRQ)**   
  Move application files that are linked to source control to any folder of the repository when working in ServiceNow Studio. Moving application files enables application developers to store supporting content, such as automated tests, in the same repository as the applications they support.