8000 Tags · netj/wtcode · GitHub
[go: up one dir, main page]

Skip to content

Tags

Tags

v0.6.0

Toggle v0.6.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Harden branch name sanitizer for slashes (fix/foo, security/bar) (#10)

Collapse repeated slashes, drop hyphens adjacent to slashes, and trim
leading/trailing slashes so slashed branch names are always valid.

Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>

v0.5.0

Toggle v0.5.0's commit message
Bump version to 0.5.0

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

v0.4.0

Toggle v0.4.0's commit message
Bump version to 0.4.0

v0.3.0

Toggle v0.3.0's commit message
Bump version to 0.3.0

v0.2.0

Toggle v0.2.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Add WTCODE_TMUX_MODE for flexible tmux integration (#2)

* Add WTCODE_TMUX_MODE for flexible tmux integration

When running inside tmux, wtcode can now use send-keys to put commands
in shell history instead of exec'ing directly. This allows restarting
tools without re-selecting the worktree.

WTCODE_TMUX_MODE values:
- send-keys: send to current pane
- split-window: create split pane with send-keys
- new-window: create new window with send-keys
- unset: exec directly (default outside tmux)

Enables optmux to control whether wtcode opens in a new window, split,
or current pane while keeping the tool command in shell history.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

* Default to WTCODE_TMUX_MODE=send-keys in tmux, add exec opt-out

When running in tmux, wtcode now defaults to send-keys mode instead
of requiring explicit WTCODE_TMUX_MODE. This makes tmux integration
zero-config for the common case.

WTCODE_TMUX_MODE values:
- send-keys (NEW default in tmux): send to current pane
- split-window: create split pane with send-keys
- new-window: create new window with send-keys
- exec (NEW): opt out and exec directly

Outside tmux, behavior unchanged (exec directly).

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

* Bump version to 0.2.0

---------

Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>

v0.1.4

Toggle v0.1.4's commit message
Bump version to 0.1.4

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

v0.1.3

Toggle v0.1.3's commit message
Update tagline to "Effortlessly launch your favorite code tool in a g…

…it worktree"

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

v0.1.2

Toggle v0.1.2's commit message
Refactor into --enter-git-worktree, add --exec, bump to v0.1.2

- Merge select and prepare into single --enter-git-worktree with local vars
- Remove wtcode_cmd global; route "$@" through --launch-code-tool
- Add --exec flag to specify command without branch (fzf selects)
- exec non-function commands, call function wrappers (e.g., claude)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

v0.1.1

Toggle v0.1.1's commit message
Fix cryptic error on fzf abort, bump to v0.1.1

Show a clean "wtcode: no branch selected" message instead of a raw
bash parameter expansion error when fzf is cancelled.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

v0.1.0

Toggle v0.1.0's commit message
Prefix internal functions with --, dispatch --flags generically

Rename internal functions (msg, select-git-branch, prepare-git-worktree,
launch-code-tool) with -- prefix to avoid clashing with launched tools.
Extract --help and --version as functions, and dispatch any --flag arg
as a function call so new flags are just new functions.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
0