What's your git style? Commit many times as a sort of change tracker/backup regardless of feature completeness or functionality, or only when something is complete and passes tests?

Mixture of :
1. End of Day commits;
2. Feature completed;
3. Feature milestone achieved;
4. WHEN IM PARANOID STUFF WILL BREAK;

Lots of tiny commits on a feature branch, then a rebase and grouping all my commits into one big feature merge commit.

commit once a year with no message

- Every time i finish a section or a function
- Before going to bed or moving somewhere

Mostly like @jacoKotze said.
If I can't complete something by the end of the day, I push it in a separate dev branch.
Most of the issues are resolved by working in a issue-specific branch, so it doesn't really matter if you commit unfinished stuff until the mergerequest is accepted.

Work for a week and commit force at 16:57 on a Friday.
#fuckthesystem