Pathwise

Manuals / Version Control (Git) for Non-Engineers / Chapter 2

Build · beginner · ~40 min · Chapter 2 of 3

The happy loop

pull → branch → edit → add → commit → push → pull request.

Path progress
50%

Step 1 of 2

Branch for the change

Never edit main directly on a team. Name branches like `docs/refund-faq`.

Branch for the changeDrag stickies · tap for tips
Study mapDrag stickies · tap for tipsKeep it shortdrag · tap →Name the waitdrag · tap →Scope locatorsdrag · tap →Trace when stuckdrag · tap →One browser firstdrag · tap →Isolate statedrag · tap →Assert the UIdrag · tap →Retry wiselydrag · tap →Seed datadrag · tap →Close the loopdrag · tap →Keep it shortdrag · tap →Name the waitdrag · tap →Scope locatorsdrag · tap →Trace when stuckdrag · tap →One browser firstdrag · tap →Isolate statedrag · tap →Pathwise hackdrag · tap →Branch for the chadrag · tap →Try thisdrag · tap →Follow the dashed drag · tap →
Docs

Example

git pull
git checkout -b docs/refund-faq
# edit files
git add .
git commit -m "Add refund FAQ"
git push -u origin HEAD

Do this now

Make a tiny edit on a branch and open a PR (or practice on a personal repo).

Was this step clear?
Chapter learning outcomes
  • Branch
  • PR

Clear these before you leave