Section on how to use git bisect to locate troublesome code

[luzpaz]

Step-by-step process that is used to locate offending code when hunting for what commit a certain bug was introduced

[3x380V]

@luzpaz, do you have something special in mind not already covered by the Pro Git book?
Also git bisect and the importance of a clean history is quite a nice reading.

[luzpaz]

Yea, it might be good to just add a section that links pro git book. I was wondering if it's of use to adapt it to the context of freecad ? Showing how a developer can test each git revision until the correct revision is arrived at

[3x380V]

I'm not aware of anything special bisecting FreeCAD code. Do you have an idea where such chapter should live? A new codedebugging directory?

[luzpaz]

Like it would be awesome if one of the FC devs would screencast themselves git bisecting an issue showing their workflow.