A good tip for developers using Git is to squash multiple commmits into one.
Why do that?
If you ever work on a task and had multiple commits because you want to be safe and track the changes while work-in-progress, your commit history will be difficult to follow.
It will be hard (and waste of time) for code reviewer, or other developers, to go through multiple commits. There will be bound to be codes that you add, then remove or edit.Continue reading →