Repository navigation
Tags
Tags
v0.4.0 — hooks require approval BREAKING CHANGE: a hook no longer runs because it exists. Commands declared in a repository's .wt.toml, or in your own config file, are shown and confirmed the first time they appear and remembered afterwards — the direnv model, inverted from the fail-open one wt shipped until now. An approval is keyed by the source's declared commands, so editing them asks again. `wt trust` approves ahead of time, `wt untrust` revokes, and a [trust] whitelist in your config file exempts trees you own outright. hooks_policy and [trust] are read from your config file and from nowhere else: the thing being gated does not get to supply the gate. There is no migration. Hooks you were already running will be asked about once. Placements that would let a repository *supply* the gate rather than pass it are refused: a worktree may not land on wt's config directory or trust store, on git's global configuration or the files it includes, or inside any repository's git directory — bare ones included, which git itself is asked about. Paths are compared with case folded and symlinks resolved, and a path that names a different directory depending on which process asks is not accepted as naming one at all. Known limits, documented in docs/configuration.md: #154, #155.
fix: handle spaces in home directory paths on Windows (#94) * fix: handle spaces in home directory paths on Windows - expandHome: support ~\ (backslash) prefix and expand $HOME/${HOME}/%USERPROFILE% via os.ExpandEnv - remove: use porcelain worktree list to avoid strings.Fields splitting paths with spaces - shellenv: shell-quote arguments in Linux script(1) invocation to preserve spaces - config template: quote $WT_PATH/$WT_MAIN in hook examples Closes #93 * fix: expand Windows %VAR% style environment variables in config paths os.ExpandEnv only handles $VAR and ${VAR}. Add expandWindowsEnv for %USERPROFILE% and similar Windows-style variables, called on Windows only. Follow-up from Codex review of #94. * fix: expand env vars in tilde paths like ~/$TEAM/worktrees The tilde branch returned early, skipping os.ExpandEnv. Now env expansion runs on all paths including those starting with ~. Follow-up from Codex review round 2. * fix: check return value of os.Stdout.WriteString (errcheck)
feat: add fuzzy matching for interactive branch selection (#81) * feat: add fuzzy matching for interactive branch selection Replace exact-substring search with fuzzy matching in all interactive selection prompts (checkout, remove, pr, mr). Uses sahilm/fuzzy library. Prompts now start in search mode for immediate typing. * docs: update examples and README for fuzzy matching * fix: add TextExample to interactive examples and fix test index The TestAllExamplesHaveConcreteSamples test requires all non-JSON examples to have a TextExample. Also fix TestRemoveJSONExampleIndex which hardcoded index [1] but the interactive example shifted it to [2].
PreviousNext