You know this situation: you are working on new feature branch of your product. A bunch of files has been changed, nothing has settled yet and lots of uncommitted changes. This is how work in progress looks like. Everything could be alright, but then you are asked to check out that high priority issue that a customer reported. What I did in this situation stash my changes with git stash save and provide a meaningful message for when I have to unstash- my changes changes branches and pull from master build the product repro the issue create a new branch for the fix implement the fix and push to the newly created branch let somebody else verify the fix go back to my previous branch git stash pop my work in progress continue working on the feature Introducing Worktrees I was reading git release notes, and I stumbled upon something I haven’t heard before in the git context: worktree.

Let’s start with a bold statement: We all love to write unit great tests for our code. More or less. — Unknown Programmer Writing unit tests for my code mostly follows this pattern Write a test and make it fail (red) Write the function to fix the test (implement function) Start over with step 1 For one of my projects, I was using jest. It’s fast now, and it has several features that I highly value.