Eric Sunshine <sunshine@xxxxxxxxxxxxxx> writes: > Is receive.denyCurrentBranch worth mentioning as an argument? Although > pushing a branch into a non-bare repo where that branch is already > checked out is normally disallowed, receive.denyCurrentBranch > overrides the safeguard. Presumably, the user has experience and > knowledge to know that "git reset --hard" will be required to sync > things up. Or the user knows that he does not have a shell access to the box in the first place. I do not see much relevance to this discussion. I would not mind "git worktree add -f" to disable the "no multiple checkouts of the same branch" safety, but I do not think it is sensible to remove "-i-o-w" and conflate everything into "--force". That would force people to disable other safety measures at the same time (e.g. protect local changes from differences between the current and next branches). -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html