BuildBeginner40 min read
2. The happy loop
Version Control (Git) for Non-Engineers · 12 pages source format
pull → branch → edit → add → commit → push → pull request.
What you'll learn
- Branch
- PR
Branch for the change
Never edit main directly on a team. Name branches like `docs/refund-faq`.
git pull
git checkout -b docs/refund-faq
# edit files
git add .
git commit -m "Add refund FAQ"
git push -u origin HEADDo this now
Make a tiny edit on a branch and open a PR (or practice on a personal repo).
Clear?
Review is the product
PRs are for humans: summary, screenshots, “how to test”.
Do this now
Write a PR description template you like.
Pro tip. Ask for review from the person who owns the area.
Clear?