If you are working on a feature branch that could take some time to finish, it helps you keep your code updated with the latest changes so that you avoid conflicts. Also, Git only takes full responsibility for your data when you commit.

When should you commit?

You commit when you have reached a codebase state you want to remember. There are a lot of reasons why you might want to remember a particular codebase state, so there can’t be hard-and-fast rules on when to commit.

Is Git commit necessary?

Yes, you need to commit your changes before you can push anything. A push (and a pull) only transfers commit contents, so something that is not committed is not transferred.