Writing good commit messages is important.
A good commit message doesn't just describe what changed, it captures why it was changed.
It can detail other approaches that were considered or tried before deciding on the end solution.
It can contain links to relevant issues, documentation pages, blog posts or videos.
It can document any manual deployment steps, or follow-up actions that will be addressed in future commits.
This all makes sense for permanent commits.
But, sometimes you may make a temporary commit that won't always remain in the codebase.
For example, if you're working in a pair or mob programming session, you want to be able to switch drivers as quickly and seamlessly as possible.
In that situation, you just need a basic commit message to share the latest changes, so a quick wip commit is fine and it can be amended later.
