---
schema_version: "1"
id: 6a9a0af3ee7fd0d2f69011ab46931f5aabd74cf7ddcc8ba8c238ae75382f6a34
title: Controlling Source Files
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/anypoint-code-builder/start-scm.md
canonical_url: https://docs.mulesoft.com/anypoint-code-builder/start-scm
source_site: docs.mulesoft.com
content_type: documentation
content_hash: ad55b39539f3979794198bc157dda1f4650b709b7c3eddf520a96a4cc2375d50
description: MuleSoft Documentation Site
latest: true
---
---
product: Anypoint Code Builder
version: master
---

# Controlling Source Files

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Use source control management (SCM) to store and share your design, integration, and implementation
projects. A useful SCM provides change history of each file and a branching methodology to maintain
project quality, full traceability, the ability to restore earlier versions of your files, and a way
to recover source code if your Anypoint Code Builder environment is lost or removed.

GitHub and the Git command line interface (CLI) are widely used in the industry and supported by VS
Code out-of-the-box, with minimal configuration. The procedures on this page show how to set up and
use GitHub for source control. VS Code extensions for other SCM systems are also available for you
to set up and use. For information, see
[SCM Providers](https://code.visualstudio.com/docs/sourcecontrol/overview#_scm-providers).

For more information, see
[Using Git source control in VS Code](https://code.visualstudio.com/docs/sourcecontrol/overview) in
the VS Code documentation. For detailed information about Git, see the
[Git documentation](https://git-scm.com/book).

## Before You Begin

Ensure that these prerequisites are in place:

- A GitHub account

  If you do not have an account, create one from the [Join GitHub](https://github.com/signup) page
  on the GitHub site.

- A Git installation on your computer

  If Git is not installed on your computer, follow the
  [Git installation instructions](https://github.com/git-guides/install-git) for your machine.

- Access to Anypoint Code Builder

  For setup and installation information, see
  [Getting Started with Anypoint Code Builder](https://docs.mulesoft.com/anypoint-code-builder/start-acb), and be sure to meet all prerequisites.

- A GitHub user name and email configuration (see
  [Configure Your Git Username and Password](#config-git))

### Configure Your Git Username and Password

Check for and configure your username and email properties so that you can add, update, and retrieve
your project files from a remote Git repo in GitHub.

1.  Meet the prerequisites in [Before You Begin](#prereqs).

2.  Open the Terminal window in the console:

    - Select **View** > **Terminal**.

    - Alternatively, press Ctrl and then press the backtick key (\`).

3.  From the Anypoint Code Builder terminal, check for any existing Git configuration by running
    this command:

    ```command
    git config --list
    ```

    - If your GitHub `user.name` and `user.email` are not listed or if no data returns, configure
      the properties:

      1.  Run this command to set your `user.name`, replacing `YourUserName` with your GitHub
          username:

          ```command
          git config –-global user.name "YourUserName"
          ```

      2.  Run this command to set your `user.email`, replacing `your@email.com` with your GitHub
          email address:

          ```command
          git config –-global user.email "your@email.com"
          ```

          If two-factor authentication is enabled on your GitHub account and you are prompted for a
          password, enter your personal access token instead of your GitHub login password. For more
          information, see GitHub documentation
          [Access GitHub with 2FA](https://docs.github.com/en/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication).

    - If your GitHub `user.name` and `user.email` are listed, you are ready to use Git to control
      your project files. For guidance with common source control tasks in VS Code, see:

      - [Set Up a Repository from Anypoint Code Builder](#set-up-repo)

      - [Sync Project Changes with Your Repository](#sync-changes)

## Set Up a Repository from Anypoint Code Builder

Set up a repo for your design, integration, or implementation project. If your project is already
set up to sync with a repo in an SCM that you want to use, no additional setup is required. You can
sync your changes without further setup. For an example, see
[Sync Project Changes with Your Repository](#sync-changes).

To set up a remote GitHub repo for your projects, the following scenarios are common:

- [Generate and Publish to a Repository in GitHub](#create-repo)

  If you have a project in Anypoint Code Builder but do not have a repo for that project, you can
  generate a repo in GitHub and publish your project files to that remote repo. The process also
  implicitly initializes a local repo.

- [Initialize and Commit Project Files to a Local Repository](#initialize-repo)

  Initializing and committing your project files into a local repo is a prerequisite to publishing
  and syncing files into a remote repo in GitHub.

- [Publish Project Files into an Empty Repository in GitHub](#publish-to-empty)

  If you have an empty repo in GitHub, you can publish your project files to the repo.

- [Publish Project Files to a Different Repository](#add-extra-repo)

  If your project is already configured to sync with a remote repo, you can configure Anypoint Code
  Builder to publish your project files to a different repo. This feature is helpful, for example,
  if you want to use your own repo for an API spec project that you imported from MuleSoft VCS or if
  you created your design project before the February 2024 release. Both types of projects
  automatically add a connection to a remote Git repo in MuleSoft VCS.

- [Clone a Project Repository into Anypoint Code Builder](#clone-repo)

  If a design, implementation, or integration project is already stored in a repo on GitHub, you can
  clone it into Anypoint Code Builder.

### Generate and Publish to a Repository in GitHub

If you have a project in Anypoint Code Builder but do not have a repo for that project, you can
generate a repo in GitHub and publish your project files to that remote repo. The process also
implicitly initializes a local repo. If you already have an empty repo in GitHub that you intend to
use for a project in Anypoint Code Builder, see
[Publish Project Files into an Empty Repository in GitHub](#publish-to-empty) to add and publish to
the repo.

1.  Meet the prerequisites in [Before You Begin](#prereqs).

2.  If your Mule project folder is closed, open the project at its _root_ directory:

    1.  Open the Command Palette.

        Show me how

        - Use the keyboard shortcuts:

          - Mac: Cmd+Shift+p

          - Windows: Ctrl+Shift+p

        - Select **View** > **Command Palette**.

    2.  Provide this command:

        ```command
        File: Open Folder...
        ```

    3.  Navigate to and select the _root_ folder for your project, for example:

        - Integration or Implementation Example

        - Design Project Example

        Example of a root folder and subdirectories of an integration or implementation project in
        Anypoint Code Builder:

        ![Project folder for an integration or implementation project](/mulesoft/current/en-us/anypoint-code-builder/_images/int-open-root.png)

        VS Code treats the root as a workspace, which enables the canvas to load properly.

        Example of the root directory for an API design project in Anypoint Code Builder:

        ![Project folder for a design project](/mulesoft/current/en-us/anypoint-code-builder/_images/int-open-root-design.png)

        The root of a project is the top-level folder that Anypoint Code Builder generates when you
        create a project. Do not navigate to the project root’s parent or ancestor directory or to
        one of its child or descendant directories.

3.  Open the Source Control panel.

    Show me how

    Click the ![](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-source-control-no-edits.png) (**Source Control**) icon in the
    activity bar or use the keyboard shortcuts:

    - Mac: Ctrl+Shift+g

    - Windows: Cmd+Shift+g

4.  In the Source Control panel, click **Publish to GitHub**.

    ![Publish repo to GitHub](/mulesoft/current/en-us/anypoint-code-builder/_images/start-scm-repo.png)

    When no repo is associated with your project, Anypoint Code Builder provides options for
    initializing a _local_ repo (**Initialize Repository**) or directly publishing your project to a
    new remote repo in GitHub (**Publish to GitHub**). Publishing to GitHub also implicitly
    initializes your local repo for the project.

5.  Provide a name for your repo in the field that opens, or use the default name that appears.

    ![Name of new repo](/mulesoft/current/en-us/anypoint-code-builder/_images/start-scm-repo-name.png)

    The default repo name matches the project name.

6.  Select a repo type (private or public).

    To protect data in your repo, select a private repo (**Publish to GitHub private repo**). This
    process commits and pushes your project files to your new repo.

7.  If prompted, select the files to publish to the repo.

    You can select all or a subset of the files of a design project, for example:

    ![Selecting files to add to the new repo](/mulesoft/current/en-us/anypoint-code-builder/_images/start-scm-select-files.png)

8.  To view your project files in a GitHub repo, click **Open on GitHub** in the popup.

    ![Opening repo in GitHub](/mulesoft/current/en-us/anypoint-code-builder/_images/start-scm-repo-open-in-github.png)

    Alternatively, open GitHub from your browser and locate your new repo.

To sync changes to project files with your repo, see
[Sync Project Changes with Your Repository](#sync-changes).

### Initialize and Commit Project Files to a Local Repository

Initializing and committing your project files into a local repo is a prerequisite to publishing and
syncing files into a remote repo in GitHub.

1.  Meet the prerequisites in [Before You Begin](#prereqs).

2.  If your Mule project folder is closed, open the project at its _root_ directory:

    1.  Open the Command Palette.

        Show me how

        - Use the keyboard shortcuts:

          - Mac: Cmd+Shift+p

          - Windows: Ctrl+Shift+p

        - Select **View** > **Command Palette**.

    2.  Provide this command:

        ```command
        File: Open Folder...
        ```

    3.  Navigate to and select the _root_ folder for your project, for example:

        - Integration or Implementation Example

        - Design Project Example

        Example of a root folder and subdirectories of an integration or implementation project in
        Anypoint Code Builder:

        ![Project folder for an integration or implementation project](/mulesoft/current/en-us/anypoint-code-builder/_images/int-open-root.png)

        VS Code treats the root as a workspace, which enables the canvas to load properly.

        Example of the root directory for an API design project in Anypoint Code Builder:

        ![Project folder for a design project](/mulesoft/current/en-us/anypoint-code-builder/_images/int-open-root-design.png)

        The root of a project is the top-level folder that Anypoint Code Builder generates when you
        create a project. Do not navigate to the project root’s parent or ancestor directory or to
        one of its child or descendant directories.

3.  Open the Source Control panel.

    Show me how

    Click the ![](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-source-control-no-edits.png) (**Source Control**) icon in the
    activity bar or use the keyboard shortcuts:

    - Mac: Ctrl+Shift+g

    - Windows: Cmd+Shift+g

4.  From the Source Control panel for your project, initialize and commit your project files to a
    local repo for your project:

    1.  In the Source Control panel, click **Initialize Repository** to generate a local repo for
        your project.

        ![Initializing a local repo for a project](/mulesoft/current/en-us/anypoint-code-builder/_images/start-scm-repo-initialize.png)

        When no repo is associated with your project, Anypoint Code Builder provides options for
        initializing a _local_ repo (**Initialize Repository**) for your project or directly
        publishing your project to a new remote repo in GitHub (**Publish to GitHub**).

    2.  Stage your files to your local repository by hovering over the **Changes** area (located
        after the **Commit** button) and clicking the ![](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-scm-add-changes.png) (plus)
        icon.

        ![Adding commit message for staged changes](/mulesoft/current/en-us/anypoint-code-builder/_images/start-scm-repo-stage-changes.png)

        Alternatively, you can stage a single file by clicking the plus icon for that file.

        Staged files move from the **Changes** area in the Source Control panel to the **Staged
        Changes** area. The UI uses the `git add` command to add changes from your working directory
        to the staging area in your local Git repo.

    3.  Provide your a commit message for the files, and then click **Commit**, for example:

        ![Commit message for staged changes](/mulesoft/current/en-us/anypoint-code-builder/_images/start-scm-repo-commit-staged.png)

5.  To publish your files to a remote repository, you can:

    - [Publish Project Files into an Empty Repository in GitHub](#publish-to-empty)

      If you have an empty repo in GitHub, you can publish your project files to the repo.

    - [Publish Project Files to a Different Repository](#add-extra-repo)

      If your project is already configured to sync with a remote repo, you can configure Anypoint
      Code Builder to publish your project files to a different repo.

### Publish Project Files into an Empty Repository in GitHub

If you have an empty repo in GitHub, you can publish your project files to the repo. This procedure
assumes that the project files are ready to stage and publish to the repo.

1.  Meet the prerequisites in [Before You Begin](#prereqs).

2.  If you have not yet initialized a local repo for your project, see
    [Initialize and Commit Project Files to a Local Repository](#initialize-repo).

3.  Open the Command Palette.

    Show me how

    - Use the keyboard shortcuts:

      - Mac: Cmd+Shift+p

      - Windows: Ctrl+Shift+p

    - Select **View** > **Command Palette**.

4.  Configure a connection from the project to your empty remote repo in GitHub:

    1.  Provide the following command to add the remote repo on GitHub:

        ```command
        Git: Add Remote...
        ```

    2.  Select **Add Remote from GitHub** from the popup menu.

        ![Adding an remote repo from GitHub](/mulesoft/current/en-us/anypoint-code-builder/_images/start-scm-oas-add-remote.png)

    3.  Provide the URL to your git repo, for example:

        ![Adding a remote repo URL from GitHub](/mulesoft/current/en-us/anypoint-code-builder/_images/start-scm-repo-add-remote-uri.png)

    4.  Provide a name for the remote, for example:

        my-acb-project-repo

        The name for the repo can match or differ from the repo name in GitHub.

5.  Click **Publish Branch**.

    ![Publish branch files in a repo on GitHub](/mulesoft/current/en-us/anypoint-code-builder/_images/start-scm-repo-publish-branch.png)

6.  Open your repo in GitHub to review the published files, for example:

    ![Project files in a repo on GitHub](/mulesoft/current/en-us/anypoint-code-builder/_images/start-scm-repo-github.png)

To sync changes to project files with your repo, see
[Sync Project Changes with Your Repository](#sync-changes).

### Publish Project Files to a Different Repository

If your project is already configured to sync with a remote repo, you can configure Anypoint Code
Builder to publish your project files to a different repo. This feature is helpful, for example, if
you want to use your own repo for an API spec project that you imported from MuleSoft VCS or if you
created your design project before the February 2024 release. Both types of projects automatically
add a connection to a remote Git repo in MuleSoft VCS. For more information, see
[Source Control for API Design Projects](https://docs.mulesoft.com/anypoint-code-builder/des-designing-api-specs#anypoint-scm).

If you are unsure whether your project is already connected to a remote repo, see
[Check for a Remote Repository URL](#check-remote).

This example assumes that you have an empty repo in GitHub. If you do not, you can create one from
GitHub. For guidance, see
[Quickstart for repositories](https://docs.github.com/en/repositories/creating-and-managing-repositories/quickstart-for-repositories)
in the GitHub documentation.

1.  Meet the prerequisites in [Before You Begin](#prereqs).

2.  If your Mule project folder is closed, open the project at its _root_ directory:

    1.  Open the Command Palette.

        Show me how

        - Use the keyboard shortcuts:

          - Mac: Cmd+Shift+p

          - Windows: Ctrl+Shift+p

        - Select **View** > **Command Palette**.

    2.  Provide this command:

        ```command
        File: Open Folder...
        ```

    3.  Navigate to and select the _root_ folder for your project, for example:

        - Integration or Implementation Example

        - Design Project Example

        Example of a root folder and subdirectories of an integration or implementation project in
        Anypoint Code Builder:

        ![Project folder for an integration or implementation project](/mulesoft/current/en-us/anypoint-code-builder/_images/int-open-root.png)

        VS Code treats the root as a workspace, which enables the canvas to load properly.

        Example of the root directory for an API design project in Anypoint Code Builder:

        ![Project folder for a design project](/mulesoft/current/en-us/anypoint-code-builder/_images/int-open-root-design.png)

        The root of a project is the top-level folder that Anypoint Code Builder generates when you
        create a project. Do not navigate to the project root’s parent or ancestor directory or to
        one of its child or descendant directories.

3.  Open the Source Control panel.

    Show me how

    Click the ![](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-source-control.png) (**Source Control**) icon in the activity bar or
    use the keyboard shortcuts:

    - Mac: Ctrl+Shift+g

    - Windows: Cmd+Shift+g
    1.  In the Source Control Panel, notice that there is a repo in the **Source Control
        Repositories** area of the panel, for example:

        ![Project source control using MuleSoft VCS](/mulesoft/current/en-us/anypoint-code-builder/_images/start-scm-oas-anypoint.png)

4.  Open the Command Palette.

    Show me how

    - Use the keyboard shortcuts:

      - Mac: Cmd+Shift+p

      - Windows: Ctrl+Shift+p

    - Select **View** > **Command Palette**.

5.  Configure a connection from the project to your repo in GitHub:

    1.  Provide the following command to add the remote repo on GitHub:

        ```command
        Git: Add Remote...
        ```

    2.  Select **Add Remote from GitHub** from the popup menu.

        ![Adding an extra remote repo from GitHub](/mulesoft/current/en-us/anypoint-code-builder/_images/start-scm-oas-add-remote.png)

    3.  Provide the URL to your git repo, for example:

        https://github.com/me/my-extra-repo.git

    4.  Provide a name for the remote, for example:

        my-extra-repo

        This name for the repo can match or differ from the repo name in GitHub.

6.  Publish your project to your extra remote repo:

    1.  In the command palette, provide the following command:

        ```command
        Git: Push to...
        ```

    2.  Select **Git: Push to…​** from the popup menu.

        ![Selecting 'Push to…​'](/mulesoft/current/en-us/anypoint-code-builder/_images/start-scm-oas-push-to.png)

    3.  Select the extra remote repo that you added, for example:

        ![Selecting the extra remote repo](/mulesoft/current/en-us/anypoint-code-builder/_images/start-scm-oas-publish-to-private-repo.png)

7.  Check for your project source files in your repo on GitHub, for example:

    ![Viewing project files in the extra remote repo](/mulesoft/current/en-us/anypoint-code-builder/_images/start-scm-oas-in-github.png)

You can now clone this project repo to easily modify and sync your changes from the UI. See
[Clone a Project Repository into Anypoint Code Builder](#clone-repo).

## Sync Project Changes with Your Repository

After your project is connected and published to a remote repo in GitHub, you can sync your changes
with that repo. If your repo is not set up yet, see
[Set Up a Repository from Anypoint Code Builder](#set-up-repo).

Use the UI or the built-in terminal to sync your changes:

- [Sync Changes from the Source Control Panel](#sync-from-ui)

- [Sync Changes from the Command Terminal](#sync-from-terminal)

### Sync Changes from the Source Control Panel

To sync changes to your files from your project’s Source Control panel:

1.  If your Mule project folder is closed, open the project at its _root_ directory:

    1.  Open the Command Palette.

        Show me how

        - Use the keyboard shortcuts:

          - Mac: Cmd+Shift+p

          - Windows: Ctrl+Shift+p

        - Select **View** > **Command Palette**.

    2.  Provide this command:

        ```command
        File: Open Folder...
        ```

    3.  Navigate to and select the _root_ folder for your project, for example:

        - Integration or Implementation Example

        - Design Project Example

        Example of a root folder and subdirectories of an integration or implementation project in
        Anypoint Code Builder:

        ![Project folder for an integration or implementation project](/mulesoft/current/en-us/anypoint-code-builder/_images/int-open-root.png)

        VS Code treats the root as a workspace, which enables the canvas to load properly.

        Example of the root directory for an API design project in Anypoint Code Builder:

        ![Project folder for a design project](/mulesoft/current/en-us/anypoint-code-builder/_images/int-open-root-design.png)

        The root of a project is the top-level folder that Anypoint Code Builder generates when you
        create a project. Do not navigate to the project root’s parent or ancestor directory or to
        one of its child or descendant directories.

2.  Open the Source Control panel.

    Show me how

    Click the ![](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-source-control.png) (**Source Control**) icon in the activity bar or
    use the keyboard shortcuts:

    - Mac: Ctrl+Shift+g

    - Windows: Cmd+Shift+g

3.  In the Source Control panel:

    1.  Stage your files to your local repository by hovering over the **Changes** area (located
        after the **Commit** button) and clicking the ![](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-scm-add-changes.png) (plus)
        icon.

        ![Adding commit message for staged changes](/mulesoft/current/en-us/anypoint-code-builder/_images/start-scm-repo-stage-changes.png)

        Alternatively, you can stage a single file by clicking the plus icon for that file.

        Staged files move from the **Changes** area in the Source Control panel to the **Staged
        Changes** area. The UI uses the `git add` command to add changes from your working directory
        to the staging area in your local Git repo.

    2.  Provide your a commit message for the files, and then click **Commit**, for example:

        ![Commit message for staged changes](/mulesoft/current/en-us/anypoint-code-builder/_images/start-scm-repo-commit-staged.png)

    3.  Click **Sync Changes** to push your changes to your remote repo on GitHub.

4.  Open the project in GitHub to check for the synced changes.

### Sync Changes from the Command Terminal

To sync changes to your files from your project’s command terminal:

1.  If your Mule project folder is closed, open the project at its _root_ directory:

    1.  Open the Command Palette.

        Show me how

        - Use the keyboard shortcuts:

          - Mac: Cmd+Shift+p

          - Windows: Ctrl+Shift+p

        - Select **View** > **Command Palette**.

    2.  Provide this command:

        ```command
        File: Open Folder...
        ```

    3.  Navigate to and select the _root_ folder for your project, for example:

        - Integration or Implementation Example

        - Design Project Example

        Example of a root folder and subdirectories of an integration or implementation project in
        Anypoint Code Builder:

        ![Project folder for an integration or implementation project](/mulesoft/current/en-us/anypoint-code-builder/_images/int-open-root.png)

        VS Code treats the root as a workspace, which enables the canvas to load properly.

        Example of the root directory for an API design project in Anypoint Code Builder:

        ![Project folder for a design project](/mulesoft/current/en-us/anypoint-code-builder/_images/int-open-root-design.png)

        The root of a project is the top-level folder that Anypoint Code Builder generates when you
        create a project. Do not navigate to the project root’s parent or ancestor directory or to
        one of its child or descendant directories.

2.  Open the Terminal window in the console:

    - Select **View** > **Terminal**.

    - Alternatively, press Ctrl and then press the backtick key (\`).

3.  At the prompt, run Git commands to add new files to your repo and to stage, commit, and push
    changes to your remote repo on GitHub.

    The following example uses `git status` to check the status of changes, `git commit` to commit
    all changed files and add a commit message, and `git push` to merge the changes into the files
    on the remote repo.

    $ git status On branch main Your branch is up to date with '011124-test-api-remote/main'.

    Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use
    "git restore <file>..." to discard changes in working directory) modified: 011124-test-api.raml

    no changes added to commit (use "git add" and/or "git commit -a")

    $ git commit -am 'my commit message' \[main bccc296\] another commit 1 file changed, 1
    deletion(-)

    $ git push Enumerating objects: 5, done. Counting objects: 100% (5/5), done. Delta compression
    using up to 8 threads Compressing objects: 100% (3/3), done. Writing objects: 100% (3/3), 944
    bytes | 944.00 KiB/s, done. Total 3 (delta 2), reused 0 (delta 0), pack-reused 0 remote:
    Resolving deltas: 100% (2/2), completed with 2 local objects. To
    https://github.com/me/my-repo.git e4156cc..bccc296 main -> main

For common Git commands, see [About Git](https://docs.github.com/en/get-started/using-git/about-git)
in the GitHub documentation, or find all commands in the
[Git command reference](https://git-scm.com/docs).

## Branch and Review Changes to a Mule Project

When multiple developers work on the same Mule project, merging changes to flow configuration XML
files is more error-prone than merging typical source code. Work on a separate branch for each
feature or fix so that concurrent changes stay isolated and conflicts are easier to resolve when you
merge.

Global elements in `global-config.xml`, such as connector configurations and connection details,
affect every flow that references them. Commit changes to this file separately from flow changes,
with a commit message that explains what changed and why, so you can roll back a global
configuration change without also reverting unrelated flow work.

When you review changes in a Mule configuration XML file, attribute reordering, namespace
declarations, and auto-generated component IDs can clutter the review process. Focus your review on
the parts that affect runtime behavior, such as connector configurations, DataWeave scripts, and
flow logic.

## Clone a Project Repository into Anypoint Code Builder

If your design, implementation, or integration project is already stored in a repo on GitHub, you
and your team members can clone it into Anypoint Code Builder. Cloning is helpful for sharing your
project, for enabling you to edit source and sync changes, and for retrieving a backup of a deleted
project. For example, you can work on the same project on different computers if your project is
stored in a repo to which you and your team have access.

1.  Open the Terminal window in the console:

    - Select **View** > **Terminal**.

    - Alternatively, press Ctrl and then press the backtick key (\`).

2.  Open the Command Palette.

    Show me how

    - Use the keyboard shortcuts:

      - Mac: Cmd+Shift+p

      - Windows: Ctrl+Shift+p

    - Select **View** > **Command Palette**.

3.  Clone the repo into the Source Control panel for your project:

    1.  Provide the following command to add the remote repo on GitHub:

        ```command
        Git: Clone
        ```

    2.  Provide the URL to your repo in GitHub, for example:

        ```command
        https://github.com/_owner_/_yourrepo_.git
        ```

        Replace the URL in the example with the URL to your repo in GitHub. The owner and repo URL
        are unique to your GitHub site.

    3.  Navigate to a directory for your new repo, and click **Select as repo Destination**.

    4.  If prompted with the request **Would you like to open the cloned repository?**, click
        **Open** to open the project.

        For cloned integration or implementation projects, you can navigate to `src`→ `main` →
        `mule` to find the config XML file or files.

To sync changes to project files with your repo, see
[Sync Project Changes with Your Repository](#sync-changes).

## Check for a Remote Repository URL

To determine whether a remote GitHub repo for your project is configured, check for a URL to the
repo:

1.  If your Mule project folder is closed, open the project at its _root_ directory:

    1.  Open the Command Palette.

        Show me how

        - Use the keyboard shortcuts:

          - Mac: Cmd+Shift+p

          - Windows: Ctrl+Shift+p

        - Select **View** > **Command Palette**.

    2.  Provide this command:

        ```command
        File: Open Folder...
        ```

    3.  Navigate to and select the _root_ folder for your project, for example:

        - Integration or Implementation Example

        - Design Project Example

        Example of a root folder and subdirectories of an integration or implementation project in
        Anypoint Code Builder:

        ![Project folder for an integration or implementation project](/mulesoft/current/en-us/anypoint-code-builder/_images/int-open-root.png)

        VS Code treats the root as a workspace, which enables the canvas to load properly.

        Example of the root directory for an API design project in Anypoint Code Builder:

        ![Project folder for a design project](/mulesoft/current/en-us/anypoint-code-builder/_images/int-open-root-design.png)

        The root of a project is the top-level folder that Anypoint Code Builder generates when you
        create a project. Do not navigate to the project root’s parent or ancestor directory or to
        one of its child or descendant directories.

2.  Open the Terminal window in the console:

    - Select **View** > **Terminal**.

    - Alternatively, press Ctrl and then press the backtick key (\`).

3.  Provide the following command:

    ```command
    git remote -v
    ```

    - If the project has one or more remote repo configurations, the command returns the URL for
      each remote, along with `push` and `fetch` information, for example:

      $ git remote -v origin https://github.com/me/my-project-repo.git (fetch) origin
      https://github.com/me/my-project-repo.git (push)

    - If no results return, a remote repo is not configured for the project.

    - If the error `fatal: not a git repo (or any of the parent directories): .git` returns, a local
      repo is not initialized for the project.

For information about `git remote` command options, see
[git-remote reference](https://git-scm.com/docs/git-remote) in the GitHub documentation.

## Remove a Remote Repository from Your Project

To remove a remote repo from your project workspace:

1.  If your Mule project folder is closed, open the project at its _root_ directory:

    1.  Open the Command Palette.

        Show me how

        - Use the keyboard shortcuts:

          - Mac: Cmd+Shift+p

          - Windows: Ctrl+Shift+p

        - Select **View** > **Command Palette**.

    2.  Provide this command:

        ```command
        File: Open Folder...
        ```

    3.  Navigate to and select the _root_ folder for your project, for example:

        - Integration or Implementation Example

        - Design Project Example

        Example of a root folder and subdirectories of an integration or implementation project in
        Anypoint Code Builder:

        ![Project folder for an integration or implementation project](/mulesoft/current/en-us/anypoint-code-builder/_images/int-open-root.png)

        VS Code treats the root as a workspace, which enables the canvas to load properly.

        Example of the root directory for an API design project in Anypoint Code Builder:

        ![Project folder for a design project](/mulesoft/current/en-us/anypoint-code-builder/_images/int-open-root-design.png)

        The root of a project is the top-level folder that Anypoint Code Builder generates when you
        create a project. Do not navigate to the project root’s parent or ancestor directory or to
        one of its child or descendant directories.

2.  Open the Source Control panel.

    Show me how

    Click the ![](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-source-control.png) (**Source Control**) icon in the activity bar or
    use the keyboard shortcuts:

    - Mac: Ctrl+Shift+g

    - Windows: Cmd+Shift+g

3.  In the Source Control panel:

    1.  Provide the following Git command to add the remote repo on GitHub:

        ```command
        Git: Remove Remote...
        ```

    2.  In the popup, select the remote repo that you want to remove.

        Your local Git repo remains because it was initialized before syncing with the remote.

## See Also

- [Introduction to Git in VS Code](https://code.visualstudio.com/docs/sourcecontrol/quickstart)