AI-powered Git collaboration network for OSS

Code with purpose, Integrate with confidence

---

</> What is GitMesh?

_{Click the video above to watch demo!}

GitMesh is a Git collaboration network designed to solve open source's biggest challenge: contributor dropout. Our AI-powered platform provides real-time branch-level insights, intelligent contributor-task matching, and automated workflows. It transforms complex codebases into clear, guided contribution journeys—fueling engagement with gamified rewards, bounties, and integration with popular open source support programs.

Our mascot (Meshy/Mesh Wolf) reflects GitMesh's core: agile, resilient, and unstoppable together. Like a pack, we thrive on teamwork — efficient, and powerful in unison.

---

</> Meet us at

OpenSource Summit Japan • 8-10 Dec 2025	OpenSource Summit Korea • 4-5 Nov 2025
OpenSearchCon Korea • 4 Nov 2025	OpenSSF Community Day Korea • 4 Nov 2025

---

</> Installation

👾 Prerequisites

Node.js is required to run the application.

1. Visit the Node.js Download Page
2. Download the "LTS" (Long Term Support) version for your operating system
3. Run the installer, accepting the default settings
4. Verify Node.js is properly installed:
   • For Windows Users:
     1. Press Windows + R
     2. Type "sysdm.cpl" and press Enter
     3. Go to "Advanced" tab → "Environment Variables"
     4. Check if Node.js appears in the "Path" variable
   • For Mac/Linux Users:
     1. Open Terminal
     2. Type this command:

        echo $PATH

     3. Look for /usr/local/bin in the output
5. Install Package Manager (pnpm)

   npm install -g pnpm

6. Install Git: Download Git

👾 Quick Start

Choose one of the following methods to get started with GitMesh:

Setup Using Git (For Developers)

This method is recommended for developers who want to:

• Stay updated with the latest changes
• Switch between different versions
• Create custom modifications

Initial Setup:

1. Clone the Repository:

   git clone https://github.com/LF-Decentralized-Trust-labs/gitmesh.git

2. Navigate to Project Directory:

   cd gitmesh

3. Install Dependencies:

   pnpm install

4. Start the Development Server:

   pnpm run dev

5. Configure Github PAT: If you’re running the project for the first time, you’ll need to configure your GitHub Personal Access Token (PAT) to authenticate and connect GitMesh to your GitHub account.

Steps to Generate and Configure PAT

1. Start the GitMesh server and open the provided localhost link.

You’ll be prompted to enter your Personal Access Token.

2. To generate a new token:

• Go to GitHub → Settings → Developer settings → Personal Access Tokens → Tokens (classic)
• Click Generate new token → Generate new token (classic)
• Select the required scopes (typically: repo, user, read:org)
• Click Generate Token
• Copy the generated token (you’ll only see it once)

3. Paste the token into the prompt on localhost when asked.

You can configure GitHub, GitLab, or both in a similar way — just make sure to use the correct platform’s token.
Tip: Keep your PAT secure. Never share or commit it in any file or codebase.

Staying Updated:

To get the latest changes from the repository:

1. Save Your Local Changes (if any):

   git stash

2. Pull Latest Updates:

   git pull 

3. Update Dependencies:

   pnpm install

4. Restore Your Local Changes (if any):

   git stash pop

Setup Using Docker

This method is recommended for users who want to:

• Run GitMesh in a containerized environment
• Isolate dependencies from the host system
• Deploy easily in production environments

Prerequisites:

• Docker must be installed on your system. Download Docker

Building Docker Images:

1. Build Production Image:

   pnpm run dockerbuild:prod

   This creates a production-ready Docker image tagged as gitmesh-ai:production and gitmesh-ai:latest.

2. Build Development Image:

   pnpm run dockerbuild

   This creates a development Docker image tagged as gitmesh-ai:development and gitmesh-ai:latest.

Running Docker Containers:

1. Run the Production Container:

   pnpm run dockerrun

   This runs the Docker container with:

   • Container name: gitmesh-ai-live
   • Port mapping: 5173:5173
   • Environment variables from .env.local file

   Note: Make sure you have a .env.local file in your project root with the required environment variables before running this command.

2. Direct Docker Run Command (Alternative):

   docker run -it -d --name gitmesh-ai-live -p 5173:5173 --env-file .env.local gitmesh-ai

Building and Running in One Step:

For production:

pnpm run dockerbuild:prod && pnpm run dockerrun

For development:

pnpm run dockerbuild && docker run -it -d --name gitmesh-ai-dev -p 5173:5173 --env-file .env.local gitmesh-ai:development

Important Notes:

• Ensure you have a .env.local file with all required environment variables
• The container exposes the application on port 5173 by default
• To stop the running container: docker stop gitmesh-ai-live
• To remove the container: docker rm gitmesh-ai-live
• To remove the image: docker rmi gitmesh-ai

👾 Troubleshooting

Git Setup Issues

If you encounter issues:

1. Clean Installation:

   # Remove node modules and lock files
   rm -rf node_modules pnpm-lock.yaml
   
   # Clear pnpm cache
   pnpm store prune
   
   # Reinstall dependencies
   pnpm install

2. Reset Local Changes:

   # Discard all local changes
   git reset --hard origin/main

Remember to always commit your local changes or stash them before pulling updates to avoid conflicts.

---

</> Contributing

We welcome contributions! Please see our Contributing Guide for details.

👾 Quick Contributing Steps:

1. Fork the repository
2. Create a new branch

git checkout -b type/branch-name

3. Make your changes
4. Sign Commit your changes (git commit -s -m 'Add some amazing feature')
5. Push to the branch (git push origin type/branch-name)
6. Submit a signed pull request

Mesh & Meshy are excited to see what amazing contributions you'll bring to the GitMesh community!

---

</> Our Maintainers

RAWx18

parvm1102

Ronit-Raj9

</> Community & Support

👾 Support Channels

Channel	Typical Response Time	Best For
Discord	Real-time	Quick questions, community discussions
Email Support	24–48 hours	Technical issues, detailed bug reports
Twitter / X	Online	Tagging the project, general updates, public reports
GitHub Issues	1–3 days	Bug reports, feature requests, feedback

---

</> Project Statistics

Metric	Value
Total Commits
Pull Requests
Issues Resolved
Latest Release

---

A Lab under the Linux Foundation Decentralized Trust – Advancing open source innovation.