Worktrunk is a CLI for Git worktree management, designed for parallel AI agent workflows
feat(branch): Add --force-delete to delete unmerged branches
Maximilian Roos2950909a961e
diff --git a/.claude-plugin/skills/worktrunk/reference/README.md b/.claude-plugin/skills/worktrunk/reference/README.mdindex 06065a117..d751a0fa5 100644--- a/.claude-plugin/skills/worktrunk/reference/README.md+++ b/.claude-plugin/skills/worktrunk/reference/README.md@@ -13,9 +13,10 @@Worktrunk is a CLI tool which makes working with git worktrees much much easier.It's designed for those running many concurrent AI coding agents.-Git worktrees let multiple agents work on a single repo without colliding; each agent-gets a separate directory. But creating worktrees, tracking paths, and cleaning-up afterward is manual. Worktrunk automates that lifecycle.+For context, git worktrees let multiple agents work on a single repo without+colliding; each agent gets a separate directory with a version of the code. But+creating worktrees, tracking paths & statuses, cleaning up, etc is manual.+Worktrunk offers transparency and automation for this lifecycle.## Quick Start@@ -66,7 +67,7 @@ wt config shell # Sets up shell integration## Automation Features-### LLM-Powered Commit Messages+### LLM-Authored Commit MessagesDuring merge operations, worktrunk can invoke a binary, such as [llm](https://llm.datasette.io/), to generate commit messages based on the diff and a configurable prompt.@@ -97,20 +98,26 @@ $ wt merge✅ Squashed @ a1b2c3d```-Set up LLM integration: run `wt config --help` to see the setup guide, or `wt config init` to create an example config file.+To set up integration: run `wt config --help` to see the setup guide, or `wt config init` to create an example config file.<details>-<summary><b>Advanced: Custom Prompt Templates</b></summary>+<summary>Advanced: Custom Prompt Templates</summary>-Worktrunk uses [minijinja templates](https://docs.rs/minijinja/latest/minijinja/syntax/index.html) for commit message prompts. Customize the prompts by setting `template` (inline) or `template-file` (external file) in the `[commit-generation]` section. Use `squash-template` / `squash-template-file` for squash commits.+Worktrunk uses [minijinja+templates](https://docs.rs/minijinja/latest/minijinja/syntax/index.html) for+commit message prompts. Customize the prompts by setting `template` (inline) or+`template-file` (external file) in the `[commit-generation]` section. Use+`squash-template` / `squash-template-file` for squash commits.-See [`config.example.toml`](config.example.toml) for complete template examples with all available variables (`git_diff`, `branch`, `recent_commits`, `commits`, `target_branch`, `repo`).+See [`config.example.toml`](config.example.toml) for complete template examples+with all available variables (`git_diff`, `branch`, `recent_commits`, `commits`,+`target_branch`, `repo`).</details>### Project Hooks-Automate common tasks by creating `.config/wt.toml` in your repository root. Run tests before merging, install dependencies when creating worktrees, start dev servers automatically.+Automate common tasks by creating `.config/wt.toml` in the repository root. Install dependencies when creating worktrees, start dev servers automatically, run tests before merging.```toml# Install deps when creating a worktree@@ -215,17 +222,19 @@ $ wt mergeWorktrunk is opinionated! It's not designed to be all things to all people. The choices optimize for agent workflows:- Lots of short-lived worktrees-- CLI-based Agents-- Local inner dev loops-- Navigated using the shell-- Commits are squashed, linear histories+- Trunk-based development+- CLI-based agents+- Inner dev loops are local+- Shell navigation+- Commits are squashed into linear histories- Maximum automation-Standard `git worktree` commands continue working fine — adopting Worktrunk for a portion of a workflow doesn't require adopting it for everything.+Adopting Worktrunk for a portion of a workflow doesn't require adopting it for+everything — standard `git worktree` commands continue working fine.## Tips-**Create an alias for your favorite agent** - Shell aliases streamline common workflows. For example, to create a worktree and immediately start Claude:+**Create an alias for an agent** - Shell aliases streamline common workflows. For example, to create a worktree and immediately start Claude:```bashalias wsl='wt switch --create --execute=claude'@@ -233,11 +242,20 @@ alias wsl='wt switch --create --execute=claude'Now `wsl new-feature` creates a branch, sets up the worktree, runs initialization hooks, and launches Claude in that directory.-**Automatic branch status in Claude Code** - The Claude Code integration shows which branches have active AI sessions. When Claude starts working, the branch shows `🤖` in `wt list`. When waiting for input, it shows `💬`. Setup instructions: [Custom Worktree Status](#custom-worktree-status).+**Automatic branch status in Claude Code** - The Claude Code integration shows+which branches have active sessions. When Claude starts working, the branch+shows `🤖` in `wt list`. When waiting for input, it shows `💬`. Setup+instructions: [Custom Worktree Status](#custom-worktree-status).-**Auto-generated commit messages** - Simon Willison's [llm](https://llm.datasette.io/) tool integrates seamlessly with worktrunk's commit generation. Install it, configure the command, and `wt merge` will automatically generate contextual commit messages. Setup guide: [LLM-Powered Commit Messages](#llm-powered-commit-messages).+**Auto-generated commit messages** - Simon Willison's+[llm](https://llm.datasette.io/) tool integrates seamlessly with worktrunk's+commit generation. Install it, configure the command, and `wt merge` will+automatically generate contextual commit messages. Setup guide: [LLM-Authored+Commit Messages](#llm-authored-commit-messages).-**Environment setup with hooks** - Each worktree is a separate directory. Use `post-create-command` to ensure consistent environments:+**Environment setup with hooks** - Use `post-create-command` (or+`post-start-command` for non-blocking) to run setup for that+path:```toml# In .config/wt.toml@@ -278,9 +296,7 @@ Experimental commands for advanced workflows. These are subject to change.- `wt beta rebase [target]` - Rebase current branch onto target- `wt beta ask-approvals` - Approve commands in project config- `wt beta run-hook <hook-type>` - Run a project hook for testing-- `wt beta select` - Interactive worktree selector (Unix only)--**Note:** Beta commands may have breaking changes between releases.+- `wt beta select` - Interactive worktree selector (Unix only, WIP)</details>@@ -332,10 +348,13 @@ wt config --help # Show LLM setup guide<summary>Configuration details</summary>**Global config** (`~/.config/worktrunk/config.toml`):+- `worktree-path` - Path template for new worktrees- `[commit-generation]` - LLM command and prompt templates+- `[projects."project-id"]` - Per-project approved commands (auto-populated)**Project config** (`.config/wt.toml` in repository root):+- `[post-create-command]` - Commands after worktree creation- `[post-start-command]` - Background commands after creation- `[pre-commit-command]` - Validation before committing@@ -352,6 +371,10 @@ worktree-path = "../{{ main_worktree }}.{{ branch }}"[commit-generation]command = "llm"args = ["-m", "claude-haiku-4-5-20251001"]++# Approved commands (auto-populated when approving project hooks)+[projects."github.com/user/repo"]+approved-commands = ["npm install", "npm test"]```**Example project config** (`.config/wt.toml`): See Project Hooks section above.@@ -368,10 +391,10 @@ Add emoji status markers to branches that appear in `wt list`. Perfect for track```bash# Set status for current branch-wt config status set "🚧"+wt config status set "🤖"# Or use git config directly-git config worktrunk.status.feature-x "🚧"+git config worktrunk.status.feature-x "💬"```**Status appears in the Status column:**@@ -390,18 +413,18 @@ dirty-with-status ≡?🤖 ./dirty-with-status b8346The custom emoji appears directly after the git status symbols.<details>-<summary><b>Automation with Claude Code Hooks</b></summary>+<summary>Automation with Claude Code Hooks</summary>Claude Code can automatically set/clear emoji status when coding sessions start and end. This shows which branches have active AI sessions.-**Easy setup:** The Worktrunk repository includes a `.claude-plugin` directory with pre-configured hooks. If you're working in this repository, the hooks are automatically available.+**Easy setup:** The Worktrunk repository includes a `.claude-plugin` directory with pre-configured hooks. When working in this repository, the hooks are automatically available.-**Manual setup for other repositories:** Copy the hooks from [`.claude-plugin/hooks/hooks.json`](.claude-plugin/hooks/hooks.json) to your `~/.claude/settings.json`.+**Manual setup for other repositories:** Copy the hooks from [`.claude-plugin/hooks/hooks.json`](.claude-plugin/hooks/hooks.json) to `~/.claude/settings.json`.-Now when you use Claude:+When using Claude:-- Sets status to `🤖` for the current branch when you submit a prompt (working)-- Changes to `💬` when Claude needs your input (waiting for permission or idle)+- Sets status to `🤖` for the current branch when submitting a prompt (working)+- Changes to `💬` when Claude needs input (waiting for permission or idle)- Clears the status completely when the session ends**Status from other terminal:**@@ -449,13 +472,15 @@ worktree-path = "../worktrees/{{ main_worktree }}/{{ branch }}"### Shell Integration-Worktrunk can automatically configure your shell:+Worktrunk can automatically configure the shell:```bashwt config shell```-This adds shell integration to your config files (supports Bash, Zsh, and Fish). The integration enables `wt switch` to change directories and `wt remove` to return to the previous location.+This adds shell integration to config files (supports Bash, Zsh, and Fish). The+integration enables `wt switch` to change directories and `wt remove` to return+to the previous location.For manual setup instructions, see `wt config shell --help`.@@ -464,7 +489,7 @@ For manual setup instructions, see `wt config shell --help`.Worktrunk is in active development. The core features are stable and ready for use. While the project is pre-1.0, the CLI interface and major features are unlikely to change significantly.<details>-<summary><b>Developing</b></summary>+<summary>Developing</summary>### Releases@@ -493,9 +518,9 @@ Worktrunk executes commands in three contexts:1. **Project hooks** (`.config/wt.toml`) - Automation for worktree lifecycle2. **LLM commands** (`~/.config/worktrunk/config.toml`) - Commit message generation-3. **--execute flag** - Commands you provide explicitly+3. **--execute flag** - Commands provided explicitly-Commands from project hooks and LLM configuration require approval on first run. Approved commands are saved to `~/.config/worktrunk/approved.toml`. If a command changes, worktrunk requires new approval.+Commands from project hooks and LLM configuration require approval on first run. Approved commands are saved to `~/.config/worktrunk/config.toml` under the project's configuration. If a command changes, worktrunk requires new approval.**Example approval prompt:**diff --git a/src/cli.rs b/src/cli.rsindex 48c3343e6..24ed72e98 100644--- a/src/cli.rs+++ b/src/cli.rs@@ -542,6 +542,10 @@ Switch to default in primary:#[arg(long = "no-delete-branch", action = clap::ArgAction::SetFalse, default_value_t = true)]delete_branch: bool,+ /// Delete unmerged branches+ #[arg(short = 'D', long = "force-delete")]+ force_delete: bool,+/// Run removal in foreground#[arg(long = "no-background", action = clap::ArgAction::SetFalse, default_value_t = true)]background: bool,diff --git a/src/commands/merge.rs b/src/commands/merge.rsindex b0858c4de..f932934d4 100644--- a/src/commands/merge.rs+++ b/src/commands/merge.rs@@ -197,6 +197,7 @@ pub fn handle_merge(changed_directory: true,branch_name: current_branch.clone(),no_delete_branch: false,+ force_delete: false,target_branch: Some(target_branch.clone()),};crate::output::handle_remove_output(&remove_result, Some(¤t_branch), true, false)?;diff --git a/src/commands/repository_ext.rs b/src/commands/repository_ext.rsindex 5c5717074..a1828dde8 100644--- a/src/commands/repository_ext.rs+++ b/src/commands/repository_ext.rs@@ -27,6 +27,7 @@ pub trait RepositoryCliExt {&self,branch_name: &str,no_delete_branch: bool,+ force_delete: bool,) -> Result<RemoveResult, GitError>;/// Prepare the target worktree for push by auto-stashing non-overlapping changes when safe.@@ -74,6 +75,7 @@ impl RepositoryCliExt for Repository {&self,branch_name: &str,no_delete_branch: bool,+ force_delete: bool,) -> Result<RemoveResult, GitError> {let worktree_path = match self.worktree_for_branch(branch_name)? {Some(path) => path,@@ -109,6 +111,7 @@ impl RepositoryCliExt for Repository {changed_directory,branch_name: branch_name.to_string(),no_delete_branch,+ force_delete,target_branch: None,})}diff --git a/src/commands/worktree.rs b/src/commands/worktree.rsindex 30de0bba5..f2296b33d 100644--- a/src/commands/worktree.rs+++ b/src/commands/worktree.rs@@ -150,6 +150,7 @@ pub enum RemoveResult {changed_directory: bool,branch_name: String,no_delete_branch: bool,+ force_delete: bool,target_branch: Option<String>,},}@@ -368,6 +369,7 @@ pub fn handle_switch(pub fn handle_remove(worktree_name: &str,no_delete_branch: bool,+ force_delete: bool,background: bool,) -> Result<RemoveResult, GitError> {let repo = Repository::current();@@ -380,7 +382,7 @@ pub fn handle_remove(crate::output::progress(progress_msg)?;}- repo.remove_worktree_by_name(worktree_name, no_delete_branch)+ repo.remove_worktree_by_name(worktree_name, no_delete_branch, force_delete)}impl<'a> CommandContext<'a> {diff --git a/src/main.rs b/src/main.rsindex 07062662c..870f27163 100644--- a/src/main.rs+++ b/src/main.rs@@ -271,14 +271,23 @@ fn main() {Commands::Remove {worktrees,delete_branch,+ force_delete,background,} => (|| -> Result<(), GitError> {+ // Validate conflicting flags+ if !delete_branch && force_delete {+ return Err(GitError::message(+ "Cannot use --force-delete with --no-delete-branch",+ ));+ }+let repo = Repository::current();if worktrees.is_empty() {// No worktrees specified, remove current worktreelet current_branch = repo.resolve_worktree_name("@")?;- let result = handle_remove(¤t_branch, !delete_branch, background)?;+ let result =+ handle_remove(¤t_branch, !delete_branch, force_delete, background)?;handle_remove_output(&result, None, false, background)} else {// When removing multiple worktrees, we need to handle the current worktree last@@ -309,13 +318,14 @@ fn main() {// Remove others first, then current last// Progress messages shown by handle_remove_output for all casesfor resolved in &others {- let result = handle_remove(resolved, !delete_branch, background)?;+ let result = handle_remove(resolved, !delete_branch, force_delete, background)?;handle_remove_output(&result, Some(resolved), false, background)?;}// Remove current worktree last (if it was in the list)if let Some(resolved) = current {- let result = handle_remove(&resolved, !delete_branch, background)?;+ let result =+ handle_remove(&resolved, !delete_branch, force_delete, background)?;handle_remove_output(&result, Some(&resolved), false, background)?;}diff --git a/src/output/handlers.rs b/src/output/handlers.rsindex 90da7adae..d41165cb0 100644--- a/src/output/handlers.rs+++ b/src/output/handlers.rs@@ -40,6 +40,17 @@ fn format_switch_message(result: &SwitchResult, branch: &str) -> (String, bool)}}+/// Get flag acknowledgment note for remove messages+fn get_flag_note(no_delete_branch: bool, force_delete: bool, branch_deleted: bool) -> &'static str {+ if no_delete_branch {+ " (--no-delete-branch)"+ } else if force_delete && branch_deleted {+ " (--force-delete)"+ } else {+ ""+ }+}+/// Format message for remove operation (includes emoji and color for consistency)////// `branch_deleted` indicates whether branch deletion actually succeeded (not just attempted)@@ -53,6 +64,7 @@ fn format_remove_message(changed_directory,branch_name,no_delete_branch,+ force_delete,..} = result;@@ -63,25 +75,28 @@ fn format_remove_message("Removed worktree & branch"};+ // Show flag acknowledgment when applicable+ let flag_note = get_flag_note(*no_delete_branch, *force_delete, branch_deleted);+let branch_display = branch.or(Some(branch_name));if *changed_directory {if let Some(b) = branch_display {// Re-establish GREEN after each green_bold reset to prevent color leakformat!(- "{GREEN}{action} for {GREEN_BOLD}{b}{GREEN_BOLD:#}{GREEN}, changed directory to {GREEN_BOLD}{}{GREEN_BOLD:#}{GREEN:#}",+ "{GREEN}{action} for {GREEN_BOLD}{b}{GREEN_BOLD:#}{GREEN}, changed directory to {GREEN_BOLD}{}{GREEN_BOLD:#}{GREEN:#}{flag_note}",primary_path.display())} else {format!(- "{GREEN}{action}, changed directory to {GREEN_BOLD}{}{GREEN_BOLD:#}{GREEN:#}",+ "{GREEN}{action}, changed directory to {GREEN_BOLD}{}{GREEN_BOLD:#}{GREEN:#}{flag_note}",primary_path.display())}} else if let Some(b) = branch_display {- format!("{GREEN}{action} for {GREEN_BOLD}{b}{GREEN_BOLD:#}{GREEN:#}")+ format!("{GREEN}{action} for {GREEN_BOLD}{b}{GREEN_BOLD:#}{GREEN:#}{flag_note}")} else {- format!("{GREEN}{action}{GREEN:#}")+ format!("{GREEN}{action}{GREEN:#}{flag_note}")}}@@ -173,6 +188,7 @@ pub fn handle_remove_output(changed_directory,branch_name,no_delete_branch,+ force_delete,target_branch,} = result;@@ -190,13 +206,16 @@ pub fn handle_remove_output(// Determine if we should delete the branch (check once upfront)let should_delete_branch = if *no_delete_branch {false+ } else if *force_delete {+ // Force delete requested - always delete+ true} else {// Check if branch is fully merged to targetlet check_target = target_branch.as_deref().unwrap_or("HEAD");let deletion_repo = worktrunk::git::Repository::at(primary_path);deletion_repo- .run_command(&["merge-base", "--is-ancestor", branch_name, check_target])- .is_ok()+ .is_ancestor(branch_name, check_target)+ .unwrap_or(false)};// Show progress message based on what we'll do@@ -205,9 +224,15 @@ pub fn handle_remove_output("{CYAN}Removing {CYAN_BOLD}{branch_name}{CYAN_BOLD:#}{CYAN} in background; retaining branch (--no-delete-branch){CYAN:#}")} else if should_delete_branch {- format!(- "{CYAN}Removing {CYAN_BOLD}{branch_name}{CYAN_BOLD:#}{CYAN} & branch in background{CYAN:#}"- )+ if *force_delete {+ format!(+ "{CYAN}Removing {CYAN_BOLD}{branch_name}{CYAN_BOLD:#}{CYAN} & branch in background (--force-delete){CYAN:#}"+ )+ } else {+ format!(+ "{CYAN}Removing {CYAN_BOLD}{branch_name}{CYAN_BOLD:#}{CYAN} & branch in background{CYAN:#}"+ )+ }} else {format!("{CYAN}Removing {CYAN_BOLD}{branch_name}{CYAN_BOLD:#}{CYAN} in background; retaining unmerged branch{CYAN:#}"@@ -240,25 +265,27 @@ pub fn handle_remove_output(// Delete the branch (unless --no-delete-branch was specified)let branch_deleted = if !no_delete_branch {let deletion_repo = worktrunk::git::Repository::at(primary_path);- let check_target = target_branch.as_deref().unwrap_or("HEAD");- // Use git merge-base --is-ancestor to check if branch is merged to target- let delete_result = match deletion_repo.run_command(&[- "merge-base",- "--is-ancestor",- branch_name,- check_target,- ]) {- Ok(_) => {- // Branch is an ancestor of target (fully merged), safe to delete- deletion_repo.run_command(&["branch", "-D", branch_name])- }- Err(_) => {- // Branch is not fully merged to target- Err(worktrunk::git::GitError::CommandFailed(format!(- "error: the branch '{}' is not fully merged",- branch_name- )))+ // Use git branch -D if force_delete is true, otherwise check if merged first+ let delete_result = if *force_delete {+ // Force delete - use -D directly+ deletion_repo.run_command(&["branch", "-D", branch_name])+ } else {+ let check_target = target_branch.as_deref().unwrap_or("HEAD");++ // Check if branch is merged to target using is_ancestor+ match deletion_repo.is_ancestor(branch_name, check_target) {+ Ok(true) => {+ // Branch is an ancestor of target (fully merged), safe to delete+ deletion_repo.run_command(&["branch", "-D", branch_name])+ }+ Ok(false) | Err(_) => {+ // Branch is not fully merged to target+ Err(worktrunk::git::GitError::CommandFailed(format!(+ "error: the branch '{}' is not fully merged",+ branch_name+ )))+ }}};diff --git a/tests/snapshots/integration__integration_tests__init__init_bash.snap b/tests/snapshots/integration__integration_tests__init__init_bash.snapindex 90faf44a7..b89d196e3 100644--- a/tests/snapshots/integration__integration_tests__init__init_bash.snap+++ b/tests/snapshots/integration__integration_tests__init__init_bash.snap@@ -16,7 +16,7 @@ info:LANG: CLC_ALL: CSOURCE_DATE_EPOCH: "1761609600"- WORKTRUNK_CONFIG_PATH: /var/folders/wf/s6ycxvvs4ln8qsdbfx40hnc40000gn/T/.tmpjbIi2I/test-config.toml+ WORKTRUNK_CONFIG_PATH: /var/folders/wf/s6ycxvvs4ln8qsdbfx40hnc40000gn/T/.tmpnii422/test-config.toml---success: trueexit_code: 0@@ -629,7 +629,7 @@ _wt() {return 0;;wt__remove)- opts="-C -v -h --no-delete-branch --no-background --verbose --help [WORKTREES]..."+ opts="-D -C -v -h --no-delete-branch --force-delete --no-background --verbose --help [WORKTREES]..."if [[ ${cur} == -* || ${COMP_CWORD} -eq 2 ]] ; thenCOMPREPLY=( $(compgen -W "${opts}" -- "${cur}") )return 0diff --git a/tests/snapshots/integration__integration_tests__init__init_fish.snap b/tests/snapshots/integration__integration_tests__init__init_fish.snapindex 73299ac7d..9b23b47c8 100644--- a/tests/snapshots/integration__integration_tests__init__init_fish.snap+++ b/tests/snapshots/integration__integration_tests__init__init_fish.snap@@ -16,7 +16,7 @@ info:LANG: CLC_ALL: CSOURCE_DATE_EPOCH: "1761609600"- WORKTRUNK_CONFIG_PATH: /var/folders/wf/s6ycxvvs4ln8qsdbfx40hnc40000gn/T/.tmppDJXpo/test-config.toml+ WORKTRUNK_CONFIG_PATH: /var/folders/wf/s6ycxvvs4ln8qsdbfx40hnc40000gn/T/.tmpNHq9jo/test-config.toml---success: trueexit_code: 0@@ -292,6 +292,7 @@ complete -c wt -n "__fish_wt_using_subcommand switch" -s v -l verbose -d 'Show gcomplete -c wt -n "__fish_wt_using_subcommand switch" -s h -l help -d 'Print help'complete -c wt -n "__fish_wt_using_subcommand remove" -s C -d 'Change working directory' -r -Fcomplete -c wt -n "__fish_wt_using_subcommand remove" -l no-delete-branch -d 'Keep branch after removal'+complete -c wt -n "__fish_wt_using_subcommand remove" -s D -l force-delete -d 'Delete unmerged branches'complete -c wt -n "__fish_wt_using_subcommand remove" -l no-background -d 'Run removal in foreground'complete -c wt -n "__fish_wt_using_subcommand remove" -s v -l verbose -d 'Show git commands and debug info'complete -c wt -n "__fish_wt_using_subcommand remove" -s h -l help -d 'Print help'diff --git a/tests/snapshots/integration__integration_tests__init__init_zsh.snap b/tests/snapshots/integration__integration_tests__init__init_zsh.snapindex 0860905b7..f9581b3f0 100644--- a/tests/snapshots/integration__integration_tests__init__init_zsh.snap+++ b/tests/snapshots/integration__integration_tests__init__init_zsh.snap@@ -16,7 +16,7 @@ info:LANG: CLC_ALL: CSOURCE_DATE_EPOCH: "1761609600"- WORKTRUNK_CONFIG_PATH: /var/folders/wf/s6ycxvvs4ln8qsdbfx40hnc40000gn/T/.tmpwBTqs5/test-config.toml+ WORKTRUNK_CONFIG_PATH: /var/folders/wf/s6ycxvvs4ln8qsdbfx40hnc40000gn/T/.tmpjwiWHn/test-config.toml---success: trueexit_code: 0@@ -438,6 +438,8 @@ _arguments "${_arguments_options[@]}" : \_arguments "${_arguments_options[@]}" : \'-C+[Change working directory]:path:_files' \'--no-delete-branch[Keep branch after removal]' \+'-D[Delete unmerged branches]' \+'--force-delete[Delete unmerged branches]' \'--no-background[Run removal in foreground]' \'-v[Show git commands and debug info]' \'--verbose[Show git commands and debug info]' \