Capture code snapshot during dojo session/round

[falcaopetri]

Hey there!

Context

In the last Python Dojo (the first one I've ever participated) we came up really close to a working solution to a specific problem.

One more line and I think it would solve it. But it was no trivial line, and the solution drifted to other approaches.

Well, guess we will never know if it would have worked out.

Feature request

What about tracking code evolution/code snapshots during a dojo session?

Considerations

• We might want to save a commit:
  • at each save (along side running tests)
  • at each pilot switch
  • at regular time intervals
  • when tests pass
  • when tests are added
  • manually
• We might want to track:
  • pilot's nickname
  • pilot's real name
  • multiple files at once
  • event type (pilot switch, etc)
• We should consider:
  • whether the "repo" created will be shared somehow (online or not)
  • whether git blame will affect the dojo's cooperation philosophy (I'm not sure if cooperation is an oficial dojo's philosophy)
  • how this collected code snapshots will be used

Use cases

During dojo

• We came to an agreement to rollback to a previous version
• We want to create some kind of dojo statistics (?)
• We want to promove a git workflow (e.g. via manual commits)

At home

• I want to come back to a specific version and try out a new test/approach
• I want to properly debug some specific code revision
• I want to study how code evolves so rapidly

Possible implementation

Well, git? We already have multiple opportunities to save the code snapshot, e.g., during file watcher events or pilot switching.

Maybe a hook/callback approach would enable this feature and pave the way to others?