Sangam-Git

Pull requests & review

Pull requests are where changes get reviewed and approved before they join main. If you're new to the concept, read Pull requests in Learn Git first. This page covers how they work specifically on Sangam-Git.

Opening a pull request

Push your branch, then open the repository and click New pull request. Choose the base (usually main) and the compare branch (your work). Add a title and a description of what changed and why, and create it.

Reviewing

A reviewer sees the full diff — every changed line beside the old version — across the Files tab, and the discussion on the Conversation tab. They can comment on any specific line. You reply by pushing more commits to the same branch; the PR updates itself.

The human-approval gate

Sangam-Git enforces two kinds of protection before a merge:

  • AI-authored PRs always require a human approval. If a pull request was pushed with an AI-agent token, it cannot merge until a person approves it — full stop. This is structural, not a toggle.
  • Protected branches require approval too. For branches like main, you can require one or more approvals and passing CI checks before anyone can merge. Set this under the repository's Settings → Branch protection.

The PR page tells you exactly what's blocking a merge: "Review required," "Checks required," "Conflicts," or "Ready to merge."

Risk lanes

Before anyone even opens the diff, Sangam-Git flags pull requests that touch sensitive areas — authentication, payments, personal data, database migrations, dependencies, or secrets. A PR that changes your Razorpay integration or a user-data table is marked so reviewers slow down where it counts. Large changes are flagged too, with a nudge to split them for easier review.

AI help on a PR (optional)

Each of these runs only when you click, on that PR's diff, and prints the model and cost:

  • AI summary — what this PR does, in a paragraph.
  • AI review — bounded, high-confidence findings only: real bugs and weakened checks, never style nitpicks.
  • Config explained — plain-English explanation of JSON/YAML changes.

If the branch changes after a summary or review, Sangam-Git marks it stale and offers to regenerate.

Merging

When approvals and checks are satisfied, choose how to merge:

  • Create a merge commit — keeps every commit on your branch.
  • Squash and merge — combines your branch into one tidy commit on main.

After merging, delete the branch — its work is safely in main.

Comments and approvals as a record

Every approval records who approved and when. If you push new commits after an approval, reviewers can withdraw and re-approve. Together with the audit log, this gives you a clear trail of who agreed to what.

In practice: open a focused PR, let a human (and optionally AI) review it, address comments by pushing more commits, and merge once it's approved and green.