Getting comfortable with version-control branches without creating a branch for every tiny change

I'm learning Git branches and have somehow turned a small personal project into a forest of branches named `test`, `new-test` and `fix-final`. I know branches are useful for isolating risky changes, but creating one for every spelling correction seems silly. How do you decide what belongs on a separate branch when working alone, and when should a short-lived branch be deleted after merging?

  • programming-help
  • comfortable
  • version
  • control
58

4 replies · Sort: Best

Best

No conversations include a reply from the original poster.