Git & GitHub vs Postman Comparison for Beginners

# Git basics
git init
git add .
git commit -m "first commit"
git branch -M main
git remote add origin https://github.com/user/repo.git
git push -u origin main

Typical workflow:
1. Create a branch
2. Make changes
3. Stage and commit
4. Push to GitHub
5. Open a pull request
6. Review and merge

# Example API request (curl form)
GET https://api.example.com/users/1
Headers:
  Accept: application/json
  Authorization: Bearer <token>

// Postman test script
pm.test("Status is 200", function () {
  pm.response.to.have.status(200);
});
pm.test("Has a name", function () {
  pm.expect(pm.response.json().name).to.be.a("string");
});

Quick comparison:
Git + GitHub  → code history, collaboration
Postman       → API requests, tests, docs
Both          → used in the same project
Not competing → they solve different problems

Beginner mistakes:
- Thinking Git and Postman are alternatives
- Skipping Git basics before GitHub
- Not saving Postman requests as collections
- Testing APIs without checking status codes
- Pushing code without meaningful commits

Combined workflow:
1. Create feature branch (git checkout -b feature/api)
2. Write code and commit
3. Push to GitHub
4. Test the new endpoint in Postman
5. Add API tests to the collection
6. Open a pull request
7. Merge after review

Beginner checklist:
□ I can make a commit and push it
□ I can create a branch and open a PR
□ I can send a GET request in Postman
□ I can add headers and auth
□ I can write a simple test in Postman
□ I can run tests in CI (Newman)