Sangam-Git

Putting it together: a day on a team

You've met all the pieces — repo, commit, branch, clone, push, pull, pull request, merge. Here's how they fit into one normal working day at a software team. Follow this rhythm and you'll look like you've done it for years.

Let's say you're at a startup in Bengaluru building a food-delivery app, and today's task is to add GST to the invoice.

1. Start from the latest

You already cloned the repo when you joined. Each morning, get your teammates' latest work:

git switch main
git pull

Now your main matches the team's.

2. Make a branch for your task

Never build on main. Create a branch named for the task:

git switch -c feat/gst-invoice

3. Do the work, committing in small pieces

Write some code. When one meaningful step is done, commit it. Repeat.

git add invoice.js
git commit -m "Add 18% GST line to the invoice total"

git add invoice_test.js
git commit -m "Add tests for GST rounding"

Small commits with clear messages make your pull request easy to review.

4. Push your branch

Share it with the server so you can open a pull request:

git push -u origin feat/gst-invoice

5. Open a pull request

On Sangam-Git, click New pull request: base main, compare feat/gst-invoice. Write what changed and why. Create it.

Sangam-Git may add an AI summary and flag that this touches billing — a risk lane — so your reviewer pays extra attention.

6. Review and respond

Your teammate reviews. They comment: "GST should not apply to delivery charges — can you exclude that line?" Good catch. You fix it on your laptop and push again:

git add invoice.js
git commit -m "Exclude delivery charge from GST"
git push

The pull request updates automatically. Your reviewer re-checks and approves.

7. Merge

With approval (and CI checks passing), click Squash and merge. Your work is now part of main. The feature is officially in the product. 🎉

8. Clean up

Delete the finished branch:

git switch main
git pull                       # bring in your just-merged work
git branch -d feat/gst-invoice

And you're ready for the next task, starting again from step 1.

The loop, in one glance

pull  →  branch  →  commit, commit  →  push  →  pull request
  ↑                                                    │
  └──────────  merge  ←  approve  ←  review  ←─────────┘

A few habits that make you great

  • Pull before you start and before you push. Fewer conflicts, fewer surprises.
  • Commit small, message clearly. Your teammates (and future you) will thank you.
  • One branch per task. Don't mix an unrelated fix into your feature branch.
  • Read your own diff before opening a PR. You'll catch half your mistakes yourself.

That's the whole game. Every team tweaks the details, but this loop — branch, commit, push, review, merge — is how software gets built, from a two-person startup to the largest companies in the world.