Using Fluent source control in ServiceNow Studio

---
title: Using Fluent source control in ServiceNow Studio
description: Use Git commands and other source control features in ServiceNow Studio to manage changes to an application across a development team.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/application-development/servicenow-studio-classic/fluent-sc-using-fluent-source-control.html
release: australia
product: ServiceNow Studio Classic
classification: servicenow-studio-classic
topic_type: concept
last_updated: "2026-09-10"
reading_time_minutes: 2
keywords: [Fluent source control]
breadcrumb: [Fluent source control in ServiceNow Studio, Source control integration, Use, ServiceNow Studio, Build, AI Workflow Factory Prime, Agentic app development, Building applications]
---

# Using Fluent source control in ServiceNow Studio

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

After initializing a local Git repository in ServiceNow Studio, you can perform Git commands from the Changes tab \[Omitted image "servicenow-ide-source-control-icon.png"\] Alt text: or command palette, including but not limited to the following commands.

<table><thead><tr><th>

Command

</th><th>

Description

</th></tr></thead><tbody><tr><td>

Checkout to \(\[Omitted image "servicenow-ide-more-actions-icon.png"\] Alt text: &gt; **Checkout to...**\) Command palette: **Git: Checkout to...**

</td><td>

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.

</td></tr><tr><td>

Clone \(\[Omitted image "servicenow-ide-more-actions-icon.png"\] Alt text: &gt; **Clone**\) Command palette: **Git: Clone**

</td><td>

Clone a remote repository to add an application to your workspace.For more information, see [Clone a Git repository from ServiceNow Studio](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/servicenow-studio-classic/fluent-sc-clone-git-repository.md).

</td></tr><tr><td>

Commit \(\[Omitted image "servicenow-ide-commit-icon.png"\] Alt text:\) Command palette: **Git: Commit**

</td><td>

Commit your staged changes to the local repository. Enter a commit message to describe your changes.

</td></tr><tr><td>

Create branch \(**\[Omitted image "servicenow-ide-more-actions-icon.png"\] Alt text:** &gt; **Branch** &gt; **Create branch...**\)Command palette: **Git: Create branch...**

</td><td>

Add a branch to a repository and check it out.

</td></tr><tr><td>

Discard \(\[Omitted image "servicenow-ide-discard-icon.png"\] Alt text:\)Command palette: **Git: Discard Changes**

</td><td>

Discard changes to undo modifications to an application.

</td></tr><tr><td>

Fetch \(\[Omitted image "servicenow-ide-more-actions-icon.png"\] Alt text: &gt; **Fetch**\)Command palette: **Git: Fetch**

</td><td>

Fetch to sync commits and branches from the remote repository into the local repository.

</td></tr><tr><td>

Pull \(\[Omitted image "servicenow-ide-more-actions-icon.png"\] Alt text: &gt; **Pull**\)Command palette: **Git: Pull**

</td><td>

Pull to merge the latest changes from the remote repository into the local repository.

</td></tr><tr><td>

Push \(\[Omitted image "servicenow-ide-more-actions-icon.png"\] Alt text: &gt; **Push**\)Command palette: **Git: Push**

</td><td>

Push your committed changes to the remote repository.

</td></tr><tr><td>

Stage \(\[Omitted image "servicenow-ide-stage-icon.png"\] Alt text:\) Command palette: **Git: Stage Changes**

</td><td>

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.

</td></tr><tr><td>

Stash \(\[Omitted image "servicenow-ide-more-actions-icon.png"\] Alt text: &gt; **Stash**\)Command palette: **Git: Stash**, **Git: Pop**, **Git: Drop**, **Git: List**, **Git: Apply**, **Git: Clear**

</td><td>

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 **Stash** &gt; **Apply** to reapply your changes in your working directory.

</td></tr></tbody>
</table>## 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 \[Omitted image "servicenow-ide-source-control-icon.png"\] Alt text:. 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

The commit history for a branch is listed in the Commits section of the Changes tab \[Omitted image "servicenow-ide-source-control-icon.png"\] Alt text: and includes details about the commits. To see the commit history for a file, navigate to the Explorer view \[Omitted image "servicenow-ide-file-explorer-icon.png"\] Alt text:, select the file, and expand the Timeline section. When you select a commit, a Diff editor comparing the changes opens.

## Repository changes

To update the remote repository an application is connected to, you can use the `Git: Update remote origin` command from the command palette and enter a different remote repository URL.

**Parent Topic:**[Fluent source control in ServiceNow Studio](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/servicenow-studio-classic/fluent-source-control-sn-studio.md)