This is really what I was looking for to implement in git repositories, work in multiple branches at the same time in my engineering projects !! Thank you ! :)
@ChristerBlomqvist
2 жыл бұрын
I really like your presentation style and especially that you show the actual underlying git commands.
@HunterRoMike
7 сағат бұрын
Great presentation. Howveer I find git worktrees pretty useless, especially when working on huge projects with heavy IDEs. I'd rather just commit all changes, use a descriptive commit message, chenge branch and fix whatever bug needs to be fixed, and then just check out the original branch and git reset --soft HEAD~1 and continue working on whatever feature I was working on before.
@ahirusan1147
Жыл бұрын
Thank you for this tutorial, it makes years I was looking for that feature!
@bassam.2023
2 жыл бұрын
Useful tutorial, especially because you showed how things work in the background, that is, via the command line. Thanks!
@neessaa8713
2 жыл бұрын
10/10 tutorial! thank you very much!
@GitKraken
2 жыл бұрын
Glad it was helpful!
@dbt6572
Жыл бұрын
Thanks, Dwayne. Very clear.
@a_maxed_out_handle_of_30_chars
Жыл бұрын
thank you, simple and to the point :)
@Shinwe
6 ай бұрын
Great and simple, thank you.
@mateustymoniuk
Жыл бұрын
You saved me from getting lost in stashes and temporary local branches, thanks a lot!
@chrisidema
2 жыл бұрын
Pretty neat. I hate stash as I can forget about it. I often create a new branch for temporary commits.
@graciborski
11 ай бұрын
Beautiful introduction
@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.
@danylohromyak5228
Жыл бұрын
Why does everyone use a terminal instead of a built-in vscode git GUI?
@gersonscheffer2765
2 жыл бұрын
great video.However I think commit with a message and after use squash it is more practical than using worktree
@amansagar4948
2 ай бұрын
How is that different from cloning the repository again into a separate folder ?
@isaacressler8177
2 ай бұрын
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.
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'`
@kristupasqwert9888
2 жыл бұрын
How would you link your node_modules with a new branch to avoid reinstalling deps?
@GitKraken
2 жыл бұрын
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
2 жыл бұрын
Haven't tested it but I think a symbolic link to an existing node_modules directory from new branch might work.
@trusabaka9747
3 ай бұрын
@@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.
@dannywidjaya7943
20 күн бұрын
how is this better than simply cloning to a different folder? less mental load.
@apefu
2 жыл бұрын
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.
Пікірлер: 30