Pull requests: proposing your changes

A pull request (PR) is how you ask for your branch to be reviewed and added to the main project. It's the front door for every change on a team — a place to show your work, get feedback, and get approval before it becomes official.

The name is a little confusing at first. A "pull request" is you saying: "Here are my commits on this branch. Please review them and pull them into main." You're requesting that your work be pulled in.

Why not just push to `main`?

On a serious project, nobody pushes straight to main. Instead:

You do your work on a branch (say feat/gst-invoices).
You open a pull request from that branch into main.
A teammate reviews it — reads the changes, leaves comments, suggests fixes.
Once it looks good, someone approves and it gets merged into main.

This means every change is seen by at least one other human before it reaches the working version. Bugs get caught. Knowledge spreads. The main branch stays trustworthy.

Opening a pull request

First push your branch:

git push -u origin feat/gst-invoices

Then, on Sangam-Git, open the repo and click New pull request. You pick:

base — where you want your work to go (usually main).
compare — your branch (feat/gst-invoices).

Write a clear title and a description of what changed and why. Then create it.

What a review looks like

Your reviewer sees every changed line, side by side with the old version (a diff). They can:

Comment on a specific line: "This will fail if the cart is empty — can you add a check?"
Ask questions, suggest improvements, or approve.

You respond by pushing more commits to the same branch — the PR updates automatically. This back-and-forth continues until everyone's happy.

Approval and merge

When the reviewer is satisfied, they approve. Then the PR can be merged — your commits become part of main, and the feature is officially in the project. (Merging has its own page.)

Pull requests on Sangam-Git

Sangam-Git adds one important rule for the age of AI coding tools: if a pull request was written by an AI agent (like Claude Code or Cursor), it is clearly labelled, and a human must approve it before it can merge. This isn't a setting someone can forget — it's built into the system. AI can propose; a person decides.

Sangam-Git can also give you an AI-written summary of a PR, flag risky changes (touching payments, auth, or personal data), and explain confusing config files in plain English — so review is faster without being careless.