Skip to content

[Feature]: Worktree branch naming other than t3code #3651

Description

@tomjn

Before submitting

  • I searched existing issues and did not find a duplicate.
  • I am describing a concrete problem or use case, not just a vague idea.

Area

apps/desktop

Problem or use case

When creating worktrees T3 Code creates branch names that include t3code/ prefixes e.g. t3code/fix-map-info-choose-button-layout

This causes problems though as it leaks tooling and doesn't follow convention.

I see that #3044 is asking for renaming, but in this case I just want to set the default to something other than t3code/ e.g. fix/ or bug/

Proposed solution

A setting I can change, or for the t3code/ prefix to be dynamic based on what is in the branch e.g. fix/ modify/ add/ feature/ etc

Why this matters

Because this means I can't use T3 Code worktrees for most of the projects I'm working on

Smallest useful scope

A settings field with t3code/ that lets me modify the default

Alternatives considered

No response

Risks or tradeoffs

No response

Examples or references

No response

Contribution

  • I would be open to helping implement this.

Activity

  1. added
    enhancementRequested improvement or new capability.
    needs-triageIssue needs maintainer review and initial categorization.
    on Jul 2, 2026
  2. juliusmarminge commented on Jul 20, 2026

    @juliusmarminge
    Member

    Closing as a duplicate of #272, the canonical configurable t3code/ branch-prefix request. The active implementation is PR #3954.

  3. added
    duplicateThis issue or pull request already exists
    and removed
    needs-triageIssue needs maintainer review and initial categorization.
    on Jul 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    duplicateThis issue or pull request already existsenhancementRequested improvement or new capability.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions