--- 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 --- # Legacy - Link an application or application-customization to source control # Legacy - Link an application or application-customization to source control {#ariaid-title1} * Versão de lançamento: Australia * * Atualizado 12 de mar. de 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 min. de leitura Linking an application or application-customization to source control allows application developers to manage changes from a Git repository. ## Antes de Iniciar Importante: Starting with the Xanadu release, the legacy version of ServiceNow Studio is being prepared for future deprecation. It will be hidden and no longer activated on new instances but will continue to be supported. For details on the deprecation process, see the [Deprecation Process \[KB0867184\]](https://support.servicenow.com/kb_view.do?sysparm_article=KB0867184) article in the Now Support Knowledge Base. Try building and editing apps in the current version of ServiceNow Studio instead. For more information, see [ServiceNow Studio](https://servicenow-prod.fluidtopics.net/HJE5fDsb~bjmVZ9BqGtS8w "ServiceNow Studio provides a unified experience for all ServiceNow development activities, enabling admins and developers to extend base system solutions and create custom apps with ease. Use ServiceNow Studio to build apps and app files with integrated tools, access and edit app metadata in scoped and global apps, and package app changes for deployment, all in one powerful development tool."). * Role required: admin * Learn more about [Managing application-customizations](https://servicenow-prod.fluidtopics.net/eC7fr6tvn0tDaU~EbtecVA "You can manage your company's customizations for applications that belong to other organizations or a scoped ServiceNow plug-in."). * Create a dedicated Git repository for the application. For increased security, enable multi-factor authentication for the Git repository. * Generate an access token that the source control integration can use instead of a password and multi-factor authentication passkey. Search for personal access token on [GitHub](https://help.github.com) or [GitLab](https://docs.gitlab.com). * Restrict permissions on the access token to allow read and write access to the Git repository. * Verify that the non-production instance has network access to the Git repository. * Ensure that users add the email address to their respective Users Table (ServiceNow sys_user) records that they use in their commits to the Git repository. * Learn more: [Legacy - Migrate completed update set history to Source Control](https://servicenow-prod.fluidtopics.net/6KL0JsIRxgwYSqLbCPkAZA "When linking to Source Control, this feature allows application developers the choice of migrating the information in completed update sets to Source Control history.") {#t_LinkAnApplicationToSourceControl__ul_wqq_ddl_p5} ## Por Que e Quando Desempenhar Esta Tarefa The source control integration does not support linking to an application or customization on a production instance. Instead, install applications on a production instance from the application repository, an update set, or the ServiceNow Store. ## Procedimento 1. Open the application you want to link to source control in Studio. 2. Navigate to Source ControlLink to Source Control. Studio displays the Link to Source Control dialog box. 3. Enter the connection details for the Git repository. {#t_LinkAnApplicationToSourceControl__table_s3x_2fl_p5__entry__2} | Field | Description | |-|-| | Network protocol | HTTPS or SSH credential type that enables secure channel data exchange. | | URL | The URL to the Git repository where you want to save application files. For SSH protocol, use command to generate private key `ssh-keygen -t rsa -m PEM -b 4096 -C "email@address"`. Nota: If the Git repo URL for SSH provided by your Git server does not work, check with your Git server owner or provider for the correct URL. There may be additional specifications such as scheme protocol prefixes, port numbers, and so on, required for your Git repo URL to function. | | Credential | The credential to be used with the selected protocol. See [Getting started with Credentials](https://www.servicenow.com/docs/access?context=credentials-getting-started&version=australia&pubname=australia-platform-security&ft:locale=en-US) to learn more about creating credentials. Nota: If you select the SSH network protocol, enter a valid credential of the SSH private key type. If you select the https protocol, enter a valid credential of the Basic Auth credentials type. | | Branch | The repository branch to work on within the application. | | MID Server Name | The name of the existing MID Server to link through. Nota: Use a separate MID Server to prevent conflicts with Discovery activities. Be sure that the MID server user can create files to the sys_attachment table and that the table can accept files of the "bundle" type. Linking or [importing](https://servicenow-prod.fluidtopics.net/nWW2tgcSBUhb4aQMJ5YrXg "Import an application or application-customization from a source control repository to continue developing it on this instance.") an application through a MID Server enables access to repositories behind a firewall. See the [Using MID Server with source control](https://servicenow-prod.fluidtopics.net/ILonX1FwG8JWLRORKyK9AQ "The ServiceNow MID Server enables communication and the movement of data between a ServiceNow instance and external applications, data sources, and services.") and [MID Server](https://www.servicenow.com/docs/access?context=mid-server-landing&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US) topics to learn more | | Default email | The committer email address is defined by the sys_user record if available. But if a committer's sys_user record email field is empty, the system generates an alternate email (username@instancename.service-now.com). You can also enter a default email address and change it later. To use that default email address in all cases, select the check box. | | Commit Comment | An optional description of the repository or application. | [Tabela 1. Source control connection details] {#t_LinkAnApplicationToSourceControl__table_s3x_2fl_p5} Nota: All application developers on the instance share a single set of repository credentials. 4. Click Submit. The system validates the connection and user credentials and displays a success message. All application developers on the instance can use the linked Git repository to manage changes. {#t_LinkAnApplicationToSourceControl__steps_ely_1gl_p5} * **[Legacy - Using MID Server with source control](https://servicenow-prod.fluidtopics.net/ILonX1FwG8JWLRORKyK9AQ)** The ServiceNow® MID Server enables communication and the movement of data between a ServiceNow instance and external applications, data sources, and services. **Tópicos relacionados** * [Getting started with credentials](https://www.servicenow.com/docs/access?context=credentials-getting-started&version=australia&pubname=australia-platform-security&ft:locale=en-US)