# What Version Control System Does Supermemory Use? Git Repository Guide

> Discover that Supermemory uses Git, the leading version control system. Explore the supermemoryai/supermemory GitHub repository for insights into their development workflow.

- Repository: [supermemory/supermemory](https://github.com/supermemoryai/supermemory)
- Tags: how-to-guide
- Published: 2026-03-25

---

**Supermemory uses Git**, the distributed version control system, hosted on GitHub under the `supermemoryai/supermemory` repository.

The Supermemory project relies exclusively on Git for source code management, utilizing standard Git workflows for branching, continuous integration, and release management. As a Turbo monorepo orchestrated with `bun` scripts, the entire codebase assumes a Git-based source tree for task running and change detection.

## Evidence of Git in the Repository Structure

Several configuration files confirm that Supermemory is tracked by Git and hosted on GitHub.

### Git Configuration Files

The `.gitignore` file in the repository root defines which files and directories Git excludes from version control, such as build artifacts and dependency folders. This is a standard Git configuration file that only appears in Git-managed projects.

Additionally, the [`README.md`](https://github.com/supermemoryai/supermemory/blob/main/README.md) provides contribution guidelines that reference Git commands and GitHub workflows, further confirming Git as the underlying VCS.

### Monorepo Integration with Git

Supermemory organizes its codebase as a Turbo monorepo, where Git integration is essential for the build pipeline. The [`turbo.json`](https://github.com/supermemoryai/supermemory/blob/main/turbo.json) configuration relies on Git to detect changes across workspaces, enabling optimized task execution based on which packages have been modified since the last commit.

Individual applications within the monorepo contain [`package.json`](https://github.com/supermemoryai/supermemory/blob/main/package.json) files—such as [`apps/web/package.json`](https://github.com/supermemoryai/supermemory/blob/main/apps/web/package.json)—that define scripts assuming Git availability for versioning and release automation.

## Working with Supermemory's Git Repository

Since Supermemory follows standard Git conventions, you can interact with the repository using familiar commands.

### Cloning and Branch Management

Begin by cloning the repository and examining the available branches:

```bash

# Clone the repository

git clone https://github.com/supermemoryai/supermemory.git
cd supermemory

# List all branches

git branch -a

# Create a new feature branch

git checkout -b feature/awesome-update

```

### Committing Changes and Opening Pull Requests

After modifying code, stage your changes and submit them through GitHub:

```bash

# Stage changes and commit

git add .
git commit -m "Add awesome update"

# Push the branch to GitHub

git push origin feature/awesome-update

# Open a pull request via the GitHub web UI or CLI

gh pr create --title "Awesome Update" --body "Description of changes"

```

These commands function identically to any standard Git project because Supermemory maintains a conventional repository structure without custom VCS abstractions.

## Git in the Continuous Integration Workflow

Supermemory's CI/CD pipeline assumes a Git environment. The combination of Turbo and `bun` scripts operates within Git workspaces to cache builds and manage dependencies. Every pull request triggers workflows that depend on Git metadata for change detection and versioning, while release tags are managed through standard Git commands.

## Summary

- **Supermemory uses Git** exclusively for version control, hosted on GitHub at `supermemoryai/supermemory`.
- The repository contains standard Git configuration files including `.gitignore` and documentation in [`README.md`](https://github.com/supermemoryai/supermemory/blob/main/README.md).
- File paths such as [`apps/web/package.json`](https://github.com/supermemoryai/supermemory/blob/main/apps/web/package.json) and [`turbo.json`](https://github.com/supermemoryai/supermemory/blob/main/turbo.json) reveal deep integration with Git-based workflows and monorepo management.
- Contributors use standard Git commands (`git clone`, `git checkout`, `git commit`, `git push`) alongside the GitHub CLI (`gh`) for pull requests.
- The Turbo monorepo configuration leverages Git hashing to optimize builds across multiple applications.

## Frequently Asked Questions

### Does Supermemory use Git or another version control system?

Supermemory uses **Git** exclusively. The presence of `.gitignore`, GitHub remote URLs, and the repository's commit history confirm that Git is the sole version control system. There is no evidence of Mercurial, SVN, or other VCS tools in the source tree.

### Where is the Supermemory Git repository hosted?

The Supermemory Git repository is hosted on **GitHub** at `https://github.com/supermemoryai/supermemory`. This is evident from the repository's URL structure, the presence of GitHub-specific workflow files, and the remote origin configuration used when cloning.

### How does Supermemory handle version control in its monorepo structure?

Supermemory implements **Git-based version control** across its Turbo monorepo. The [`turbo.json`](https://github.com/supermemoryai/supermemory/blob/main/turbo.json) file uses Git to determine which packages have changed between commits, enabling incremental builds. Additionally, [`package.json`](https://github.com/supermemoryai/supermemory/blob/main/package.json) files in directories like `apps/web/` contain scripts that interact with Git for versioning and release automation.

### What Git workflow does Supermemory recommend for contributors?

Supermemory follows the standard **GitHub Flow** workflow. Contributors should fork the repository, create feature branches using `git checkout -b feature/name`, commit changes with descriptive messages, push to GitHub, and open pull requests using either the web interface or the `gh pr create` command. All changes are reviewed and merged through GitHub's pull request system.