Worktrunk is a CLI for Git worktree management, designed for parallel AI agent workflows
docs(faq): scope the worktree-lock advice to removal (#3601)
Maximilian Roosb84305190620
diff --git a/docs/content/faq.md b/docs/content/faq.mdindex f58050f1e..261fbc7eb 100644--- a/docs/content/faq.md+++ b/docs/content/faq.md@@ -177,7 +177,7 @@ Worktrunk can delete **worktrees** and **branches**. Both have safeguards.`wt remove` mirrors `git worktree remove`: it refuses to remove worktrees with uncommitted changes (staged, modified, or untracked files). The `--force` flag removes the worktree anyway, discarding all of those changes.-For worktrees containing precious ignored data (databases, caches, large assets), use `git worktree lock`:+To protect a worktree from removal entirely (say it holds a local database), lock it:{{ terminal(cmd="git worktree lock ../myproject.feature --reason __WT_QUOT__Contains local database__WT_QUOT__") }}diff --git a/plugins/worktrunk/skills/worktrunk/reference/faq.md b/plugins/worktrunk/skills/worktrunk/reference/faq.mdindex fffae01e4..a650363c6 100644--- a/plugins/worktrunk/skills/worktrunk/reference/faq.md+++ b/plugins/worktrunk/skills/worktrunk/reference/faq.md@@ -170,7 +170,7 @@ Worktrunk can delete **worktrees** and **branches**. Both have safeguards.`wt remove` mirrors `git worktree remove`: it refuses to remove worktrees with uncommitted changes (staged, modified, or untracked files). The `--force` flag removes the worktree anyway, discarding all of those changes.-For worktrees containing precious ignored data (databases, caches, large assets), use `git worktree lock`:+To protect a worktree from removal entirely (say it holds a local database), lock it:```bashgit worktree lock ../myproject.feature --reason "Contains local database"diff --git a/skills/worktrunk/reference/faq.md b/skills/worktrunk/reference/faq.mdindex fffae01e4..a650363c6 100644--- a/skills/worktrunk/reference/faq.md+++ b/skills/worktrunk/reference/faq.md@@ -170,7 +170,7 @@ Worktrunk can delete **worktrees** and **branches**. Both have safeguards.`wt remove` mirrors `git worktree remove`: it refuses to remove worktrees with uncommitted changes (staged, modified, or untracked files). The `--force` flag removes the worktree anyway, discarding all of those changes.-For worktrees containing precious ignored data (databases, caches, large assets), use `git worktree lock`:+To protect a worktree from removal entirely (say it holds a local database), lock it:```bashgit worktree lock ../myproject.feature --reason "Contains local database"