With worktrees, you can just git cherry-pick and git reset to fix the mistake. If you accidentally commit some changes to the wrong clone, you’ll have to port them over by hand (if they’re simple) or by using patch.
#GITHUB UPSTREAM SMARTGIT FULL#
With full clones, you would have to push one repo to the remote and then pull it on the other.
You can share changes between worktrees (as long as they’re committed to at least the local repository). Worktrees are implemented using hard links, so they are lightweight and fast (whereas separate git clones copy down the full repository). You could git clone two entirely separate repositories, but worktrees are better: Many IDEs allow opening multiple projects at once, but each must be in its own directory. In these cases, it can be helpful to run multiple test suites in parallel. In a large project with very good test coverage, some test suites can take a long time to run-far beyond a convenient amount of time to sit and wait for them to finish. So why would you want one (or more) worktrees? Here a few good reasons: Run Tests While Working on Another Branch You can create this directory anywhere on the same filesystem, but it should be somewhere outside of your main repository directory! You can then proceed to use the worktree directory as usual, checking out branches, pushing upstream, etc. 
new-worktree-dir as though it were a clone of your repository. All you need to do is set up a new worktree like this: git worktree add. And in fact, Git introduced the worktree feature not too long ago (as of version 2.5, released July 2015).Ī Git worktree gives you an extra working copy of your repository, and it’s almost as easy as creating a new branch. I was about to make a full clone of the repository, but I decided to see if Git had a better solution. Recently, I was in a situation in which I really needed two separate copies of my Git repository.
0 kommentar(er)
