allow merging a non-current worktree

Open
  • Is something wrong?
#1,637 15 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
git, rust
Domain
cli, devtools

Research direction

Start by reading the wt merge command and comparing it with other commands that operate on non-current worktrees. The issue asks which options could allow merging a non-current worktree but does not choose an approach or define completion; clarify the desired behavior before implementation.

Written by the indexing model from the issue text.

Description

currently, we allow most commands to operate in worktrees other than the current

is wt merge the only exception?

what are some options for allowing this?

Dominant language
Rust
Stars
8.8k
Forks
315
Avg merge
1d 6h
Merged PRs (30d)
204

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from max-sixty/worktrunk

All issues in max-sixty/worktrunk

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.