gh-worktree
A CLI tool that helps you manage Git worktrees. Built as a GitHub CLI (gh) extension, but works standalone.
Dependencies: git, gh
Table of Contents
Quick Start
pip install gh-worktree
Or with uv:
uvx gh-worktree
Or download the PEX file from the releases page.
See recipes for hooks and templates.
Capabilities
| Feature | Description |
|---|---|
| Bare repository initialization | Clean separation of git metadata from worktrees |
| Lifecycle hooks | Custom scripts at key points with checksum validation |
| Global + project config | Hooks and templates at both levels |
| PR worktrees | Create worktrees directly from GitHub PRs |
| Project bootstrapping | Auto-copy hooks/templates from repo on init |
| Worktree templates | Pre-configured files copied to new worktrees |
| Environment variables | Template variables with allowlist support |
How It Works
Directory Structure
After initializing a repository (e.g., gh-worktree):
gh-worktree/
.bare/ # Bare git repository
.git # Points to .bare/
.gh/
worktree/
hooks/ # Project-level hooks
templates/ # Project-level templates
config.json # Project configuration
my-new-worktree/ # Created worktrees
README.md
...
Hooks
Hooks are executable scripts that run at specific lifecycle points. They can be configured at:
- Global level:
~/.gh/worktree/hooks/(or parent directories outside the project) - Project level:
.gh/worktree/hooks/(copied from repo on init if present)
Execution order: global hooks first, then project hooks.
| Hook | Executes At | Description |
|---|---|---|
pre_init |
Global only | Before initializing a repository for worktrees |
post_init |
Global + Project | After initializing a repository for worktrees |
pre_checkout |
Global + Project | Before checking out a PR or existing branch as a worktree |
post_checkout |
Global + Project | After checking out a PR or existing branch as a worktree |
pre_create |
Global + Project | Before creating a new worktree (branch) |
post_create |
Global + Project | After creating a new worktree (branch) |
pre_remove |
Global + Project | Before removing a worktree |
post_remove |
Global + Project | After removing a worktree |
Hooks must be executable and allowed (via checksum validation) to run.
Example: post_create hook
A hook for this project might look something like:
#!/usr/bin/env bash
WORKTREE_NAME="$1" # Full worktree name
BASE_REF="$2" # Format: remote/branch
WORKTREE_NAME_NORMALIZED="$3" # Worktree name with non-alphanumeric characters replaced by dashes
pushd "$WORKTREE_NAME"
uv venv
uv sync --group dev
prek install -f
popd
Templates
Files in .gh/worktree/templates/ are copied to new worktrees before post-hooks execute.
Tip: Add template files to .gitignore.
Templates support environment variable substitution using ${ENVVAR_NAME} syntax. Allowlist variable names in ~/.gh/worktree/config.json under allowed_envvars.
Provided variables:
| Variable | Description |
|---|---|
REPO_NAME |
Name of the git repository |
REPO_DIR |
Absolute path of the repo / project directory |
WORKTREE_NAME |
Name of the new worktree |
WORKTREE_NAME_NORMALIZED |
Worktree name with non-alphanumeric chars replaced by dashes |
WORKTREE_DIR |
Absolute path of the worktree directory |
Example: JetBrains project name template
Set a unique project name per worktree in JetBrains IDEs:
File: .gh/worktree/templates/.idea/.name
${REPO_NAME}.${WORKTREE_NAME_NORMALIZED}
Result in worktree: .idea/.name contains gh-worktree.feat-my-branch
Commands
Run gh-worktree without any arguments for usage information.
init — Initialize a repository for worktrees
Spec: init <repository_uri> [optional_clone_dir] [--yes]
Initializes a repository for use with worktrees. Similar to git clone — specify a directory name as the second argument, or it defaults to the repository name.
--yes: Automatically execute new or modified hooks without prompting
create — Create a new worktree
Spec: create <worktree_name> [base_ref] [--yes]
Creates a new worktree. Defaults to the default branch of the GitHub repository. Optionally specify a base reference.
--yes: Automatically execute new or modified hooks without prompting
checkout — Checkout a PR or branch as a worktree
Spec: checkout [--remote=<name>] [--yes] <branch_name|pr_number|pr_url>
Quickly create a worktree for a PR or existing branch. Works with fork PRs regardless of remote configuration.
--yes: Automatically execute new or modified hooks without prompting
remove — Remove a worktree
Spec: remove [--force] [--yes] <worktree_name>
Aliases: rm
Removes a worktree. Git refuses to delete worktrees with unmerged commits unless --force is used.
--yes: Automatically execute new or modified hooks without prompting
install — Install gh-worktree
Spec: install [--alias=<name>] [--gh-ext] [--path-bin] [--force]
Installs gh-worktree as a GitHub CLI extension or to your PATH. Without options, prompts for installation method.
--gh-ext: Install asghextension--path-bin: Install to~/.local/binor~/bin--alias: Custom name (e.g.,wktr)--force: Overwrite existing installation
Installation
Tested on Linux. Requires Python 3.10+ for PEX.
As a GitHub CLI extension (gh)
- Download the latest release binary.
- Make executable:
chmod +x gh-worktree - Install:
./gh-worktree install --gh-ext - Test:
gh worktree
Standalone
- Download the latest release binary or PEX.
- Make executable:
chmod +x gh-worktree* - Install:
./gh-worktree install --path-binor./gh-worktree.pex install --path-bin - Test:
gh-worktree version
Aliasing
./gh-worktree install --alias=wktr --path-bin
wktr version
From source
git clone https://github.com/bjester/gh-worktree.git
cd gh-worktree
uv venv
source .venv/bin/activate
uv sync --group dev
make dist/gh-worktree
./dist/gh-worktree install --path-bin
AI Disclosure
LLMs were used in the development of this project, mostly for brainstorming and bootstrapping code, particularly tests. The contribution proportion is roughly 80 / 20, human and AI code respectively. This may change over time as I try out agents!
License
MIT :: Copyright 2026 Blaine Jester
Metadata
Release files for gh-worktree 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| gh_worktree-0.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Release files / gh_worktree-0.4.0-py3-none-any.whl
| Download URL | gh_worktree-0.4.0-py3-none-any.whl |
|---|---|
| Size | 29.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
32449983d4edc1ad8284f79388f0ccb16246676412782add4944b444f19d435c
|
|
BLAKE2b-256 checksum How to use checksums |
1ea77dc8deeb11aefae67595fc750b05e85528c2f20c2b86f6166b5a6ba865ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 20, 2026.
Transparency log