Ever needed to simply send a temporary commit without having to think about its message, wait for prehooks and/or trigger any pipelines? The WIP commit is here to save you!

ITNEXT is a platform for IT professionals, developers, and technology enthusiasts, offering articles, tutorials, and insights on a wide range of topics, including software development, cloud computing, and machine learning. With a focus on practical solutions and real-world applications, ITNEXT provides actionable advice and best practices for navigating the complexities of modern technology landscapes. Developers can learn about  technologies, explore hands-on tutorials, and stay up-to-date on the latest industry trends through ITNEXT's engaging and informative content.

ITNEXT

Learn about the WIP commit in Git, how to create one, and the aliases associated with it. Save your work instantly with the WIP commit and easily switch between tasks.

Multitask like a pro with the WIP commit

The technique can lead to commiting some data that should never be pushed into the repository. It’s better to just commit often, every time with a small changes subset.
Commits can be merged into one when merging a feature branch if you want to.
You can modify existing commits before you push them.
I would say that you never want to commit anything without checking everything in the diff view. Reviewing every change before commiting improves code quality and gets rid of all „dumps”, „console.logs” etc.

If you find yourself doing this often, I’d recommend looking into <a href="https://git-scm.com/docs/git-worktree" target="_blank" rel="noopener nofollow">git worktrees</a>. Allows you to have multiple branches or commits checked out at once.