Should I submit my Git/worktree workflow improvements to upstream?

[kossnocorp]

Hey!

I developed a few Git/worktrees workflow improvements and am wondering if you want to see those in upstream. If so, I can polish the code and send PR(s).

The improvements:

• Worktrunk integration
• Use branch names for worktrees
• Branch prefix setting

Worktrunk Integration.

It adds a setting to use Worktrunk (wt CLI) to manage worktrees.

How Worktrunk Integration Works

1. It adds a new "Worktrees" section with a "Worktrunk" setting that probes the wt binary similar to git.

2. When enabled (off by default), instead of following the regular worktrees workflow and creating a worktree in ~/.t3, it uses wt switch --create --json <branch-name> which uses Worktrunk settings and hooks.

3. The default Worktrunk configuration would create a worktree in ../<project-name>.<worktree-name>/ which also matches VS Code worktrees feature behavior.

The commit: kossnocorp@5862f9a

Use Branch Names for Worktrees

It makes T3 Code use the generated branch names for worktrees instead of random ids, so <path>/t3code-deb4bb4e/ -> <path>/t3code-add-branch-prefix-setting.

It synergizes with Worktrunk integration and produces clean paths and easily recognizable names in the OS windows selection (e.g., GNOME dashboard), and recent projects list, etc.:

The commit: kossnocorp@1b344d1

Branch Prefix Setting

It adds a setting that allows changing the default t3code/ prefix.

For my workflow I use an empty string "", so worktrees have clean paths, e.g., ~/code/t3code.expand-new-thread-prompt instead of ~/code/t3code.t3code-expand-new-thread-prompt.

The commit: kossnocorp@25aca0f

[drawmeanelephant]

Of course you should.

[mikenrafter]

#6719 is related.