Use VS Code's worktree InputBox UI when checking out a PR in a worktree

[Copilot]

"Checkout in Worktree" opened the OS save dialog, which is awkward (especially on Windows) and inconsistent with VS Code's built-in Git: Create Worktree... flow that uses an inline InputBox.

Changes — src/github/worktree.ts

• Replace showSaveDialog with createInputBox in checkoutPRInWorktree, mirroring the built-in worktree UI: pre-filled editable path, prompt "Please provide a worktree path", ignoreFocusOut, and an inline folder-picker button (QuickInputButtonLocation.Inline, folder codicon) that opens showOpenDialog to pick a parent directory and re-joins the worktree name.
• Default path now follows the built-in convention <parentDir>/<repoBasename>.worktrees/pr-<number> (was <parentDir>/pr-<number>), matching what users see from Git: Create Worktree....
• Pre-select the trailing pr-<number> segment via valueSelection for quick rename.
• Warn on collision with an existing worktree using repository.state.worktrees and InputBoxValidationSeverity.Warning (non-blocking, matching built-in).

Public signature of checkoutPRInWorktree and the subsequent "open in current/new window" prompt are unchanged.

const worktreePath = await promptForWorktreePath(repositoryToUse, worktreeName, defaultWorktreePath);
if (!worktreePath) {
    return; // User cancelled
}
const worktreeUri = vscode.Uri.file(worktreePath);

[alexr00]

@copilot update branch and resolve conflicts.

[Copilot]

@copilot update branch and resolve conflicts.

Merged main and resolved the conflict in src/github/worktree.ts in b6ef67b. Both sides used the same default path convention; kept the worktreeName variable so the prompt helper can pre-select the trailing pr-<number> segment.

[alexr00]

@copilot This is not what I was looking for. I was thinking there would be some "create worktree" command that could be run instead of showing all of our own input boxes.

[Copilot]

@copilot This is not what I was looking for. I was thinking there would be some "create worktree" command that could be run instead of showing all of our own input boxes.

Could you clarify which command you have in mind? The only worktree command exposed by VS Code's built-in Git extension is git.createWorktree, and its signature is (repository?: Repository) — it runs its own branch picker followed by its own path input box and doesn't accept a pre-selected branch/commitish (source). Invoking it would force the user to pick the PR branch manually from the list, losing the "checkout this PR in a worktree" entry point.

A few options I can see:

1. Invoke git.createWorktree after we fetch the PR ref, and accept that the user still has to pick the branch from the built-in quick pick.
2. Keep our own input box (this PR), but drop the custom widgets and just reuse the built-in path-picker logic via the Repository.createWorktree API we already call.
3. Request a new API on the Git extension side (e.g. git.createWorktree accepting { commitish, branch }) so we can hand off the whole UI to it.

Which of these matches what you had in mind, or is it something else?

[alexr00]

@copilot

vscode-pull-request-github/src/@types/git.d.ts

Lines 302 to 303 in b6ef67b

	createWorktree?(options?: { path?: string; commitish?: string; branch?: string }): Promise<string>;
	deleteWorktree?(path: string, options?: { force?: boolean }): Promise<void>;

??

[Copilot]

@copilot

vscode-pull-request-github/src/@types/git.d.ts

Lines 302 to 303 in b6ef67b

	createWorktree?(options?: { path?: string; commitish?: string; branch?: string }): Promise<string>;
	deleteWorktree?(path: string, options?: { force?: boolean }): Promise<void>;

??

Got it — the path parameter is optional and createWorktree returns the resolved path. Removed all of our custom UI in ee8fb42 and now just call repository.createWorktree({ commitish, branch }), using the returned path for the follow-up "open in current/new window" prompt. The Git extension picks the location (respecting the user's saved worktree root) and handles path collisions itself.