When I’m working solo, (which usually means I’m doing the initial scoping and prototyping of some sort of feature and/or system), my “git workflow” is usually a shove it all into master affair. When I switch off to team work I often find myself in a situation where I’ve done a done of work without branching first. That’s where
git move comes to the rescue.
Okay, one more…
Ever commit something only to immediately realize that you're on the wrong branch?
Use "git move <branch>". pic.twitter.com/fKpZTRkdRu
— coderabbi™[for rent] (@coderabbi) September 4, 2017