How to Use Git Worktree | Checkout Multiple Git Branches at Once

Watch this step-by-step tutorial to learn how to leverage Git worktree and speed up your workflow. This video includes a Git worktree example, so you can learn how to use this feature to checkout and work on multiple Git branches simultaneously. We will also cover how to use Git worktree list, Git worktree add, and Git worktree remove, and provide a few tips to simplify managing multiple branches at once.
GitLens+, featured at the end of this video, makes working with Git worktree intuitive, visual, and easier. Sign up for GitLens+ free: bit.ly/3NyFClN
Navigate with chapters:
0:00 Git Worktree Introduction
0:17 Use Case for Git Worktree
1:48 Git Worktree Concept Explained
2:59 Git Worktree List
3:16 Git Worktree Add
5:49 Git Worktree Remove
7:33 Using Worktrees in GitLens+
#gitworktree #gitworktreeexample #gitworktreeadd #gitworktreelist #gitworktreeremove #howtousegitworktree #git #gitlens #vscode

[@ChristerBlomqvist]

I really like your presentation style and especially that you show the actual underlying git commands.

[@bassam.2023]

Useful tutorial, especially because you showed how things work in the background, that is, via the command line. Thanks!

[@ahirusan1147]

Thank you for this tutorial, it makes years I was looking for that feature!

[@dbt6572]

Thanks, Dwayne. Very clear.

[@a_maxed_out_handle_of_30_chars]

thank you, simple and to the point :)

[@Shinwe]

Great and simple, thank you.

[@neessaa8713]

10/10 tutorial! thank you very much!

[@GitKraken]

Glad it was helpful!

[@mateustymoniuk]

You saved me from getting lost in stashes and temporary local branches, thanks a lot!

[@graciborski]

Beautiful introduction

[@chrisidema]

Pretty neat. I hate stash as I can forget about it. I often create a new branch for temporary commits.

[@jacques-dev]

Does GitKraken support worktrees? I made a new worktree from the command line called `main`, and I can push pull fetch etc. just fine from the CLI. But when I open the repo in GitKraken and try to push or pull I get the following error: `could not determine remote for 'refs/remotes/origin/main'`

[@yoavgro3]

I don't understand how the new work tree relates to remote. can you explain how can I push this worktree, create a pr on branches there later, etc.

[@gersonscheffer2765]

great video.However I think commit with a message and after use squash it is more practical than using worktree

[@kristupasqwert9888]

How would you link your node_modules with a new branch to avoid reinstalling deps?

[@GitKraken]

I believe the same way you would normally when working in a branch. This is just a way to move a copy of a branch to another folder and should not cause breaking changes to the node workflow. Ultimately the .git folder is tracking these branches as it always does, just has multiple referenced at once.

[@radekkokon3720]

Haven't tested it but I think a symbolic link to an existing node_modules directory from new branch might work.

[@trusabaka9747]

@@GitKraken It could be a good idea for you to show the same what you have shown here with the actual say, React, project. How it will work (or not?) when the worktree is checked out? Thank you.

[@danylohromyak5228]

Why does everyone use a terminal instead of a built-in vscode git GUI?

[@amansagar4948]

How is that different from cloning the repository again into a separate folder ?

[@isaacressler8177]

In a lot of ways it's the exact same, however it enables tools like VSC to support multiple copies, like he showed. If that doesn't have any value to you it's not a tool for you.

[@ruixue6955]

1:10
1:22
2:50 3 git worktree commands
3:02 git worktree list
3:16 git worktree add
6:13 git worktree remove

[@apefu]

I am very surprised how annoyed I get by there being no space at the end of PS1.

[@plopplop.]

I'm annoyed by the `~` in your command line when you're not actually in your home directory.