---
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


---

# Using Fluent source control in ServiceNow Studio

# Using Fluent source control in ServiceNow Studio {#ariaid-title1}

Release version: Australia  
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 Using Fluent source control in ServiceNow Studio

Fluent source control in ServiceNow Studio enables administrators to manage application changes collaboratively using Git commands directly within the Studio environment.
This integration supports version control and team coordination by linking applications to remote Git repositories and providing key source control operations.
Show full answer Show less  

## Key Features

* **Git Repository Initialization:** Start by initializing a local Git repository for your application to enable source control operations.
* **Git Commands in Studio:** Perform essential Git operations through the Changes tab or command palette, including:
  * **Checkout:** Switch branches or create and push new branches. Only one branch per repository can be checked out on an instance.
  * **Clone:** Clone remote Git repositories to add applications to your workspace.
  * **Commit:** Commit staged changes locally with descriptive messages.
  * **Create Branch:** Add and switch to new branches to manage parallel development.
  * **Discard Changes:** Undo uncommitted modifications.
  * **Fetch \& Pull:** Sync and merge changes from the remote repository.
  * **Push:** Upload committed changes to the remote repository.
  * **Stage Changes:** Select changes to include in the next commit.
  * **Stash:** Temporarily save uncommitted changes and manage them with pop, drop, list, apply, and clear subcommands.
* **Merge Conflict Resolution:** Conflicting files appear under Merge conflicts in the Changes tab, allowing review and resolution by accepting current, incoming, both changes, or manual editing.
* **Commit History:** View commit history per branch in the Changes tab and per file in the Explorer's Timeline section, with a Diff editor to compare changes.
* **Repository Management:** Update the remote repository URL connected to an application using the Git: Update remote origin command.

## What You Can Expect

By using Fluent source control in ServiceNow Studio, ServiceNow administrators can effectively manage application lifecycle and collaboration through integrated Git workflows. This reduces manual source control tasks, helps maintain code integrity, enables easy tracking of changes, and simplifies conflict resolution within the ServiceNow development environment, enhancing team productivity and application quality.  
Use Git commands and other source control features in ServiceNow Studio to manage changes to an application across a development team.

Currently, only admins can use Fluent source control in ServiceNow Studio.

## Git commands {#fluent-sc-using-fluent-source-control__git-commands}

After initializing a local Git repository in ServiceNow Studio, you can perform Git commands from the Changes tab ![]() or command palette, including but not limited to the following commands.
{#fluent-sc-using-fluent-source-control__git-commands__entry__2}

| Command | Description |
|-|-|
| Checkout to (![]() \> Checkout to...) Command palette: Git: Checkout to... | Check out another branch from the repository. Select the branch from the list or create a branch and push it to the remote repository. Only one branch per repository can be checked out at a time on an instance as a sandbox in Developer Sandboxes. |
| Clone (![]() \> Clone) Command palette: Git: Clone | Clone a remote repository to add an application to your workspace. For more information, see [Clone a Git repository from ServiceNow Studio](https://www.servicenow.com/docs/DuYJSNIFwOh9AhORnerV0A "Clone a remote Git repository to collaborate on applications in Fluent source control in ServiceNow Studio."). |
| Commit (![]()) Command palette: Git: Commit | Commit your staged changes to the local repository. Enter a commit message to describe your changes. |
| Create branch (![]()BranchCreate branch...) Command palette: Git: Create branch... | Add a branch to a repository and check it out. |
| Discard (![]()) Command palette: Git: Discard Changes | Discard changes to undo modifications to an application. |
| Fetch (![]() \> Fetch) Command palette: Git: Fetch | Fetch to sync commits and branches from the remote repository into the local repository. |
| Pull (![]() \> Pull) Command palette: Git: Pull | Pull to merge the latest changes from the remote repository into the local repository. |
| Push (![]() \> Push) Command palette: Git: Push | Push your committed changes to the remote repository. |
| Stage (![]()) Command palette: Git: Stage Changes | Stage the changes in your working directory that you want to commit. When you stage changes, files move from the Changes list to the Staged Changes list. |
| Stash (![]() \> Stash) Command palette: Git: Stash, Git: Pop, Git: Drop, Git: List, Git: Apply, Git: Clear | Stash all uncommitted changes to save them in your working directory locally and come back to them later. The pop, drop, list, apply, and clear subcommands are supported when stashing. Select StashApply to reapply your changes in your working directory. |
[Table 1. Git commands in ServiceNow Studio]

## Merge conflicts {#fluent-sc-using-fluent-source-control__git-merge-conflicts}

If there's a conflict between local and remote changes in a file, the file is listed under Merge conflicts in the Changes tab ![](). You can review conflicts in the editor and resolve them by accepting the current or incoming change, both, or manually editing the file.

## Commit history {#fluent-sc-using-fluent-source-control__git-history}

The commit history for a branch is listed in the Commits section of the Changes tab ![]() and includes details about the commits. To see the commit history for a file, navigate to the Explorer view ![](), select the file, and expand the Timeline section. When you select a commit, a Diff editor comparing the changes opens.

## Repository changes {#fluent-sc-using-fluent-source-control__section_dh4_kj4_bcc}

To update the remote repository an application is connected to, you can use the <kbd class="ph userinput">Git: Update remote origin</kbd> command from the command palette and enter a different remote repository URL.

*[\>]: and then