Apologies as it might’ve been what you meant the first time around but I think you’ll find yourself doing a lot more commits than pushes unless you’re having to change workstation often. If you’re in a group just double check with them as to whether they’re OK with frequent pushes (this could vary a lot depending on their workflow).
If you meant commits then there are alternative ways to locally stage small changes (see Stash changes while keeping the changes in the working directory in Git - Stack Overflow for example) that don’t quite warrant a commit. Once again there’s no strict rule but you might raise a few eyebrows if you’re adding a few hundred commits to change something simple (chances are someone will have to squash them).
It might be worth thinking about this in the reverse, if you find you’ve made breaking changes you’ll likely be stepping backwards through commits to deal with it. Too many is a hassle and a waste, too few could make it harder to fix. If you are working in a group project try viewing what others have done to get an idea of their typical workflow; or, better still, just ask .