Worktrunk is a CLI for Git worktree management, designed for parallel AI agent workflows
docs: replace background-process note with pipeline ordering link (#1767)
Maximilian Rooseda8d9b53b39
diff --git a/docs/content/hook.md b/docs/content/hook.mdindex bab6381a7..8e629f395 100644--- a/docs/content/hook.md+++ b/docs/content/hook.md@@ -370,9 +370,7 @@ Both run when creating a worktree. The difference:| `pre-start` | Blocks until complete | Tasks the developer needs before working (dependency install) || `post-start` | Background, parallel | Long-running tasks that don't block worktree creation |-Many tasks work well in `post-start` — they'll likely be ready by the time they're needed, especially when the fallback is recompiling. If unsure, prefer `post-start` for faster worktree creation.--Background processes spawned by `post-start` outlive the worktree — pair them with `post-remove` hooks to clean up. See [Dev servers](#dev-servers) and [Databases](#databases) for examples.+Many tasks work well in `post-start` — they'll likely be ready by the time they're needed, especially when the fallback is recompiling. If unsure, prefer `post-start` for faster worktree creation. For finer control over execution order within `post-start`, see [Pipeline ordering](#pipeline-ordering).## Copying untracked filesdiff --git a/skills/worktrunk/reference/hook.md b/skills/worktrunk/reference/hook.mdindex b9bb56ae5..284f82ee9 100644--- a/skills/worktrunk/reference/hook.md+++ b/skills/worktrunk/reference/hook.md@@ -361,9 +361,7 @@ Both run when creating a worktree. The difference:| `pre-start` | Blocks until complete | Tasks the developer needs before working (dependency install) || `post-start` | Background, parallel | Long-running tasks that don't block worktree creation |-Many tasks work well in `post-start` — they'll likely be ready by the time they're needed, especially when the fallback is recompiling. If unsure, prefer `post-start` for faster worktree creation.--Background processes spawned by `post-start` outlive the worktree — pair them with `post-remove` hooks to clean up. See [Dev servers](#dev-servers) and [Databases](#databases) for examples.+Many tasks work well in `post-start` — they'll likely be ready by the time they're needed, especially when the fallback is recompiling. If unsure, prefer `post-start` for faster worktree creation. For finer control over execution order within `post-start`, see [Pipeline ordering](#pipeline-ordering).## Copying untracked filesdiff --git a/src/cli/mod.rs b/src/cli/mod.rsindex 87903ef17..6defeaf24 100644--- a/src/cli/mod.rs+++ b/src/cli/mod.rs@@ -1458,9 +1458,7 @@ Both run when creating a worktree. The difference:| `pre-start` | Blocks until complete | Tasks the developer needs before working (dependency install) || `post-start` | Background, parallel | Long-running tasks that don't block worktree creation |-Many tasks work well in `post-start` — they'll likely be ready by the time they're needed, especially when the fallback is recompiling. If unsure, prefer `post-start` for faster worktree creation.--Background processes spawned by `post-start` outlive the worktree — pair them with `post-remove` hooks to clean up. See [Dev servers](#dev-servers) and [Databases](#databases) for examples.+Many tasks work well in `post-start` — they'll likely be ready by the time they're needed, especially when the fallback is recompiling. If unsure, prefer `post-start` for faster worktree creation. For finer control over execution order within `post-start`, see [Pipeline ordering](#pipeline-ordering).## Copying untracked files