Hi, This fixes a small annoyance I had with git-worktree. Most of the feature is explained in the patch, so I'm using the cover letter to leave a couple of notes. - Since the patch changes current behaviour of git-worktree-remove, it might break existing scripts. In that case, we might want to add a config variable and command line option to trigger that. But for the sake of simplicity, I went with making the behaviour default. I don't mind making it optional if people think that would be a better idea. - To make sure no commits are lost, the branch is not deleted if it has moved since its creation. This is a more conservative approach. An alternative would be to run 'git branch -d' directly without checking if branch has moved. This will mean new commits not in upstream branch are still preserved but if the branch is simply moved to another commit it will still be deleted. Pratyush Yadav (1): worktree: delete branches auto-created by 'worktree add' Documentation/git-worktree.txt | 9 ++++-- builtin/worktree.c | 52 ++++++++++++++++++++++++++++++++-- t/t2403-worktree-move.sh | 45 +++++++++++++++++++++++++++++ 3 files changed, 101 insertions(+), 5 deletions(-) -- 2.24.1
