When should changes be committed in TDD when using GIT for source control?

We are discussing on how to structure our development workflow with TDD within SAFE for SCRUM . Although things are well structured, it is unclear to me when should one commit changes locally, and when to push them.

Should this be done everyday/ can there be mini-commits locally made within that duration, and should they be pushed upwards? what is the standard practice?

What does the framework dictates about the "when" and the "how often"?

Solution

Consider using develop & feature branches within GIT.

Your master branch should always contain a working deployable version of the software. All 'development' can be done on a develop branch and only merged into master when ready to release.

Developers create their own feature branch and should check into this as often as they like (regularly)
When each feature is complete, merge the feature branch into Develop
When you have enough features, merge into Master for a release

The use of TDD should not affect your check-in strategy. The overall aim is to always have a working build.