# About Version Control

> Source control systems prove very handy when developing larger projects that require smooth collaboration between multiple users. You can connect Studio automation projects to GIT, SVN, or TFS by accessing **Home** (Studio Backstage View) > **Team**.

Source control systems prove very handy when developing larger projects that require smooth collaboration between multiple users. You can connect Studio automation projects to GIT, SVN, or TFS by accessing **Home** (Studio Backstage View) > **Team**.

![docs image](https://dev-assets.cms.uipath.com/assets/images/studio/standalone-docs-image-317113-eb8739a0.webp)

The source control plugins for GIT, SVN, and TFS are enabled by default in Studio. You can enable or disable them individually from **Home** (Studio Backstage View) > **Tools** > **Plugins**.

![docs image](https://dev-assets.cms.uipath.com/assets/images/studio/standalone-docs-image-317121-4e9c4a0a.webp)

When a project is open in Studio, the **Add to Source Control** button in the status bar offers shortcuts to **GIT Init**, **Copy to GIT**, **Add to TFS**, and **Add to SVN**.

We recommend adding all the [files and subfolders](https://docs.uipath.com/studio/standalone/2023.10/user-guide/about-automation-projects#about-automation-projects) in the project folder to source control (the `.local` subfolder is ignored by default). In addition, make sure there are no ignore lists such as `.gitignore` files configured in a way that excludes project files and subfolders.

Only the files and subfolders from the project folder (the folder containing the `project.json` file) can be added to source control from Studio. If you want to add files or folders from outside the project folder, you must use other source control clients.

:::note
You cannot connect to **GIT**, **TFS** and **SVN** at the same time.
:::

The [GIT Version Control](https://docs.uipath.com/studio/standalone/2023.10/user-guide/managing-projects-git#managing-projects-with-git) offers an overview and instructions on how to work with GIT-versioned projects in Studio.

The steps for checking in your projects to a **TFS** or **SVN** repository are detailed in the dedicated pages [Managing Projects with TFS](https://docs.uipath.com/studio/standalone/2023.10/user-guide/managing-projects-tfs) and [Managing Projects with SVN](https://docs.uipath.com/studio/standalone/2023.10/user-guide/managing-projects-svn).

Part of working with versioned files is the possibility to compare changes between the local version of the file and the one checked in the repository. You can do so using [Workflow Diff](https://docs.uipath.com/studio/standalone/2023.10/user-guide/using-file-diff).

If you want to compare two similar files in the same automation project, use [Compare Files](https://docs.uipath.com/studio/standalone/2023.10/user-guide/comparing-files#comparing-files), which is also available for unversioned files.

Here is an example of a GIT ignore file:

```
## Compiled source #
### 
*.com 
*.class 
*.dll 
*.exe 
*.o 
*.so  

# Packages #
## 
# it's better to unpack these files and commit the raw source 
# git has its own built in compression methods 
*.7z 
*.dmg 
*.gz 
*.iso 
*.jar 
*.rar 
*.tar 
*.zip  

# Logs and databases # 
## 
*.log 
*.sql 
*.sqlite  

# OS generated files #
## 
.DS_Store 
.DS_Store? 
._* 
.Spotlight-V100 
.Trashes 
.settings 
ehthumbs.db
Thumbs.db 
desktop.ini  

# Project files 
*.idea
/DocumentUnderstandingProcess/Tests/.pytest_cache/
/DocumentUnderstandingProcess/contentFiles/any/any/pt0/VisualBasic/.local/
/DocumentUnderstandingProcess/contentFiles/any/any/pt1/CSharp/.local/
```