Worktrunk is a CLI for Git worktree management, designed for parallel AI agent workflows
docs: replace stale module doc with pointers to canonical sources (#1759)
Maximilian Roos58b18fe6ac5d
diff --git a/src/config/commands.rs b/src/config/commands.rsindex 2b1013c7e..707c14aa2 100644--- a/src/config/commands.rs+++ b/src/config/commands.rs@@ -1,30 +1,7 @@//! Command configuration types for hook pipelines.//!-//! The data structure determines execution order:-//! - **String** → single command-//! - **Map** (TOML table) → concurrent commands-//! - **List** (TOML array) → serial pipeline (steps execute in order)-//!-//! List elements can be strings (anonymous serial steps) or maps (named commands).-//! A single-entry map is a named serial step; a multi-entry map is a concurrent group.-//!-//! Examples:-//! ```toml-//! # Single command-//! post-start = "npm install"-//!-//! # Concurrent (map)-//! [hooks.post-start]-//! build = "npm run build"-//! lint = "npm run lint"-//!-//! # Serial pipeline with concurrent stage-//! [hooks]-//! post-start = [-//! { install = "npm install" },-//! { build = "npm run build", lint = "npm run lint" }-//! ]-//! ```+//! See `wt hook --help` → "Pipeline Ordering" for user-facing docs.+//! See [`HookStep`] and [`CommandConfig`] for the internal model.use std::collections::BTreeMap;