Documentation
How to use Sangam-Git — from your first repository to CI, imports and security. Plain English, with examples from Indian teams.
How to use Sangam-Git — from your first repository to CI, imports and security. Plain English, with examples from Indian teams.
This page takes you from nothing to your first commit on Sangam-Git in a few minutes. New to Git itself? Read [Learn Git](/learn) first — this page assumes you know what a commit and a push are.
Sangam-Git is built for a world where AI coding tools write a large share of the code. You can connect Claude Code, Cursor, Copilot, Codex, Windsurf, Aider — anything that speaks MCP or webhooks — and Sangam-Git will label what they produce and keep a human in charge.
Pull requests are where changes get reviewed and approved before they join `main`. If you're new to the concept, read [Pull requests](/learn/pull-request) in Learn Git first. This page covers how they work specifically on Sangam-Git.
CI runs your tests and checks automatically on every push, so problems are caught in minutes instead of after they reach `main`. Sangam-Git's CI is designed to be set up in a few clicks — no hand-written YAML required.
You don't have to abandon your history to move to Sangam-Git. You can import an existing repository — all its commits, branches, and tags — from GitHub, GitLab, Bitbucket, or any git host, in one step.
Source control is not something you experiment with. This page explains what protects your code and your account on Sangam-Git today — not on a roadmap, in the product.
On Sangam-Git, repositories belong to an **organization**, not to a person. This one decision shapes everything about how teams and access work — so it's worth understanding.