Using Fluent source control in ServiceNow Studio

  • Release version: Australia
  • Updated July 24, 2026
  • 2 minutes to read
    • Summarize
    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

    ServiceNow Studio enables administrators to use Fluent source control with Git commands to manage application changes collaboratively across development teams. This integration supports version control directly within the Studio environment, helping to coordinate development efforts and maintain application integrity.

    Show full answer Show less

    Key Features

    • Git Command Support: Perform core Git operations such as checkout, clone, commit, create branch, discard changes, fetch, pull, push, stage changes, and stash directly within ServiceNow Studio through the Changes tab or command palette.
    • Branch Management: Ability to check out one branch per repository per instance, create new branches, and push branches to remote repositories.
    • Conflict Resolution: Merge conflicts are clearly displayed in the Changes tab, with tools to review and resolve conflicts by accepting changes or manual editing.
    • Commit History and Diff Viewer: View detailed commit history per branch and per file with a timeline and a Diff editor to compare changes, aiding in code review and audit.
    • Repository Management: Update the remote repository URL for an application using the Git: Update remote origin command, allowing flexibility in repository connections.

    Key Outcomes

    By leveraging Fluent source control in ServiceNow Studio, administrators can efficiently manage application lifecycle changes, ensure team collaboration with clear versioning and branching strategies, and resolve conflicts within the platform. This integration streamlines development workflows and maintains consistency between local and remote repositories, improving overall development productivity and code 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

    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.

    Table 1. Git commands in ServiceNow Studio
    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.
    Commit ()

    Command palette: Git: Commit

    		 Commit your staged changes to the local repository. Enter a commit message to describe your changes.
    Create branch ( > Branch > Create 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 Stash > Apply to reapply your changes in your working directory.

    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

    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

    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.