repo wt pr

​

Syntax

repo wt pr <number>

​

Arguments

• <number> (required): The GitHub pull request number

​

Requirements

​

GitHub CLI

# Install GitHub CLI (macOS)
brew install gh

# Install GitHub CLI (Linux)
sudo apt install gh

# Authenticate
gh auth login

​

GitHub Repository

• Have a GitHub remote configured
• Use GitHub as the origin remote
• Be accessible with your GitHub authentication

​

Behavior

​

1. GitHub CLI Validation

• Searches for gh command in PATH
• Displays error if not found
• Requires installation before proceeding

​

2. Repository Information

• Gets the origin remote URL from the bare repository
• Converts URL to OWNER/REPO format for GitHub CLI
• Handles both SSH and HTTPS remote URLs

​

3. Pull Request Branch Resolution

• Queries GitHub API for PR #<number>
• Extracts the head branch name (source branch of PR)
• Validates that the PR exists and is accessible

​

4. Existing Worktree Check

• Uses the PR’s branch name to construct worktree path
• If worktree exists, displays message and runs post-add hooks
• Avoids re-fetching if worktree is already present

​

5. Fetch PR Branch

• Uses Git’s pull request ref: pull/<number>/head
• Creates a local branch with the PR’s branch name
• Downloads all commits from the PR

​

6. Create Worktree

• Worktree path: <repo-root>/<branch-name>/
• Checks out the fetched PR branch
• Sets up the working directory

​

7. Tracking Configuration

• Tries to configure origin/<branch> as upstream
• Silently continues if upstream branch doesn’t exist
• Useful if PR branch exists on origin

​

8. Post-Add Hooks

• Calls post_wt_add hook with worktree path
• May navigate to the PR worktree
• May display PR information

​

Examples

​

Review Pull Request #42

# Create worktree for PR #42
repo wt pr 42

# Output:
# Created worktree for PR #42: /path/to/repo/feature-branch

​

Review and Test

# Create PR worktree
repo wt pr 123

# Navigate to it
repo wt go feature-name

# Run tests
npm test

# Review code
code .

​

Multiple PR Reviews

# Review several PRs in parallel
repo wt pr 101
repo wt pr 102
repo wt pr 103

# Switch between them
repo wt go pr-101-branch
repo wt go pr-102-branch

​

Cleanup After Review

# After reviewing and approving
repo wt rm feature-branch

# Or use the PR number if you remember the branch
repo wt list | grep "feature-branch"
repo wt rm feature-branch

​

Error Cases

​

Missing PR Number

repo wt pr

# Output:
# Error: PR number is required
# Usage: repo wt pr <number>

​

GitHub CLI Not Installed

repo wt pr 42

# Output:
# Error: 'gh' CLI is required for PR worktrees

brew install gh
gh auth login

​

PR Not Found

# Invalid or inaccessible PR number
repo wt pr 99999

# Output:
# Error: Could not determine branch for PR #99999

• The PR number doesn’t exist
• The PR is in a different repository
• You don’t have access to the PR
• The PR has been deleted

​

Failed to Fetch PR

repo wt pr 42

# Output:
# Error: Failed to fetch PR #42

• Network connectivity issues
• GitHub authentication problems
• Repository access restrictions
• Deleted or closed PR branch

​

Failed to Create Worktree

repo wt pr 42

# Output:
# Error: Failed to create worktree for PR #42

• The worktree directory already exists but isn’t tracked
• Filesystem permissions prevent directory creation
• Disk space is insufficient

​

Repository Root Not Found

# Running outside a repository
repo wt pr 42

# Output:
# Error: Not in a repo-managed repository

​

Tips and Best Practices

​

Install GitHub CLI First

# Install
brew install gh  # macOS
sudo apt install gh  # Linux

# Authenticate
gh auth login

# Verify
gh auth status

​

Finding PR Numbers

• GitHub web interface
• GitHub CLI: gh pr list
• GitHub notifications
• PR URLs: github.com/owner/repo/pull/123 → number is 123

​

Review Workflow

# 1. Create PR worktree
repo wt pr 42

# 2. Navigate to it (if not done automatically)
repo wt go pr-branch-name

# 3. Review code
git log
git diff main..HEAD

# 4. Test changes
npm install
npm test

# 5. Leave comments (using gh CLI)
gh pr comment 42 --body "LGTM!"

# 6. Clean up
repo wt rm pr-branch-name

​

Parallel Reviews

# Create worktrees for multiple PRs
repo wt pr 101
repo wt pr 102
repo wt pr 103

# Each gets its own directory
# Switch between them with 'repo wt go'

​

Branch Naming

• If PR is from feature/new-api, worktree is feature/new-api
• Branch names may include slashes
• Use repo wt list to see exact branch names

​

Existing Worktrees

• No error occurs
• Worktree is not recreated
• Post-add hooks still run
• Useful for re-entering an existing PR worktree

​

Upstream Tracking

• Enables git pull to fetch PR updates
• Works if the PR branch exists on origin
• Silently skips if branch is fork-based or doesn’t exist remotely

​

Fork-Based PRs

• The command still works
• Fetches from the PR ref directly
• Upstream tracking may not be configured
• You can still review and test the code

​

Updating PR Worktrees

# Navigate to PR worktree
repo wt go pr-branch

# Fetch and pull updates
git fetch origin pull/42/head
git merge FETCH_HEAD

​

Integration with GitHub CLI

# List PRs and create worktree
gh pr list
repo wt pr 42

# View PR details in worktree
repo wt go pr-branch
gh pr view 42

# Check CI status
gh pr checks 42

​

See Also

• repo wt add - Create regular worktrees
• repo wt list - View all worktrees
• repo wt go - Navigate to worktrees
• repo wt rm - Remove worktrees
• GitHub CLI Documentation - Learn more about gh