Worktrunk is a CLI for Git worktree management, designed for parallel AI agent workflows
fix(docs): broken anchor link in step.md (#1391)
Maximilian Roos4dfac6cde8bf
diff --git a/docs/content/step.md b/docs/content/step.mdindex 6e2ce5421..03ea78702 100644--- a/docs/content/step.md+++ b/docs/content/step.md@@ -60,7 +60,7 @@ wt step deploy --var env=staging # pass extra template variableswt step deploy --yes # skip approval prompt```-When defined in both user and project config, user aliases take precedence. Project-config aliases require [command approval](@/hook.md#command-approval) on first run (same as project hooks). User-config aliases are trusted.+When defined in both user and project config, user aliases take precedence. Project-config aliases require [command approval](@/hook.md#security) on first run (same as project hooks). User-config aliases are trusted.Alias names that match a built-in step command (`commit`, `squash`, etc.) are shadowed by the built-in and will never run.diff --git a/skills/worktrunk/reference/step.md b/skills/worktrunk/reference/step.mdindex 976aa4f39..97d49349c 100644--- a/skills/worktrunk/reference/step.md+++ b/skills/worktrunk/reference/step.md@@ -51,7 +51,7 @@ wt step deploy --var env=staging # pass extra template variableswt step deploy --yes # skip approval prompt```-When defined in both user and project config, user aliases take precedence. Project-config aliases require [command approval](https://worktrunk.dev/hook/#command-approval) on first run (same as project hooks). User-config aliases are trusted.+When defined in both user and project config, user aliases take precedence. Project-config aliases require [command approval](https://worktrunk.dev/hook/#security) on first run (same as project hooks). User-config aliases are trusted.Alias names that match a built-in step command (`commit`, `squash`, etc.) are shadowed by the built-in and will never run.diff --git a/src/cli/mod.rs b/src/cli/mod.rsindex fefa2a19c..774269ff5 100644--- a/src/cli/mod.rs+++ b/src/cli/mod.rs@@ -1053,7 +1053,7 @@ wt step deploy --var env=staging # pass extra template variableswt step deploy --yes # skip approval prompt```-When defined in both user and project config, user aliases take precedence. Project-config aliases require [command approval](@/hook.md#command-approval) on first run (same as project hooks). User-config aliases are trusted.+When defined in both user and project config, user aliases take precedence. Project-config aliases require [command approval](@/hook.md#security) on first run (same as project hooks). User-config aliases are trusted.Alias names that match a built-in step command (`commit`, `squash`, etc.) are shadowed by the built-in and will never run.