This feature is so important, that it literary caused a delay on the release of TM 3.3 for about 1 month (my instinct was pushing me on this direction since I 'knew' that this could be done, and that it would be a killer feature). Btw, there is a lot more NGit/Git support than what is shown here, but I’m sure you will see the power in the workflow described below.
Basically, TM’s backend engine will now automatically perform:
- a git pull - when the TM server starts (or it cache is rebuilt)
- a git commit followed by a git push - on every library edit (on both content and structure changes).