Now, you can delete own remote branches, and ask other authors to clean-up theirs: $ git push origin -delete branch-name This magic snippet provides all required information: $ for branch in `git branch -r -merged | grep -v HEAD` do echo -e `git show -format="%ci %cr %an" $branch | head -n 1` \\t$branch done | sort -r Would be cool to know last commit date and author. What if this branch is merged, but still used for feature development. Usually, remote repository is a big garbage heap of stale branches, if there is no responsible housekeeping person.Īfter previous git remote prune origin we should have synched list of remote branches.Īt first, we can find branches which are already merged in “master”: $ git checkout masterīut this command does not provide much information. List referenced remote branches: $ git branch -rĬlean-up outdated references: $ git remote prune originĪnd Git automatically prunes all stale references. If some of them is just abandoned stuff that you don’t need anymore, remove it with “-D” option: $ git branch -D old-abandoned-featureĪfter each git pull or git fetch command Git creates references to remote branches in local repository, but doesn’t clean up stale references. Next, decide what to do with not merged branches: $ git branch -no-merged Now, remove all outdated branches with: $ git branch -d old-merged-feature We need to know what branches are already merged in “master” and can be easily removed: $ git checkout master gitconfig Local branchesĪt first, list all local branches: $ git branch If the folder is not empty you will see an error message the command will fail.5 Moving stuff into. Note: To use this option you must select an empty folder during the file section step, (step 2 in the process). vscode-gitlens-demo-1 relative to your present working directory. Let’s also assume you have selected the next highest directory to base the new worktree entry’s folder. If you select the third option from the Command Palette drop-down menu: Create Worktree (directly in folder) for branch, you will create a new worktree entry based on your specified branch inside the target folder.įor example, let’s say you’re creating a worktree entry from the insiders branch and want to have it live in a directory called vscode-gitlens-demo-1.
While this is the most common, and least confusing way to name the directory, Git allows you to have a different name for the folder than the branch name. Up until now, you have named the target directory using the same name as the branch. How do you use Git worktree add for an existing branch using a different name than the working directory with GitLens? With Git worktree, you simply tell Git to checkout the feature branch in a different directory, outside your present working directory and change to that directory from here, you can do your work and change back to the original directory to find all your work in progress awaiting you, just as you left it. Instead of that stash and checkout flow, you can simply add a new worktree entry and change directory into the needed branch.įor example, imagine you’re working on a project inside the main branch, but need to test and approve changes applied in a feature branch. If that sounds inefficient, the makers of Git agree with you. What would happen if you suddenly have to work on a hotfix in another branch? For many people, the normal workflow would be to use Git stash to save your current work, checkout the hotfix branch, conclude that work, then re-checkout the branch you were originally on and pop your stash.
Imagine you’re in the middle of making numerous changes on a project with multiple new dependencies introduced with various WIP changes. Now, what situations might you utilize this action? The Git worktree command allows you to checkout and work in multiple Git branches simultaneously.
0 kommentar(er)
