liveBook · Manning

Git handover

As explained in "Looks Good to Me"

A remote-collaboration technique for transferring active programming work between participants through a temporary Git branch and work-in-progress commits.

Git handover transfers active programming work between remote mob-programming participants when passing the keyboard is impossible. Each driver pushes a work-in-progress commit to a temporary branch, allowing the next driver to continue quickly. section 12.2.2

Use the handover as a short, repeatable sequence:

  • Create or select a temporary branch for the shared work. section 12.2.2
  • Push a WIP commit when the current driver’s turn ends. section 12.2.2
  • Have the next driver pick up the branch and continue the session. section 12.2.2
  • Squash the WIP commits into expressive commits before merging. section 12.2.2

A smoother virtual handover

A team uses mob start, mob next, and mob done to coordinate branch handovers during a virtual mob session, reducing transition friction without pretending remote work feels identical to sharing a room. section 12.2.2

How "Looks Good to Me" covers it

How deep it goes
Defines branch handoffs, WIP commits, squashing, and automation, but does not detail branch commands or merge mechanics.
Examples
Uses temporary branches, WIP commits, and the mob start, mob next, and mob done commands.
What it assumes
Assumes familiarity with collaborative programming and Git branches while teaching the handoff workflow itself.
What you can do after
Apply Git handovers during virtual mob sessions and consolidate transient commits before merging.
How it connects
Connects remote mob programming with Git branches, work-in-progress commits, code review, and commit squashing.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of "Looks Good to Me". The section links point to the parts of the book it draws on.