git-nested

Put another repository into a folder of yours. Pull its new changes. Push your changes back.

[!NOTE] This site is also published as plain Markdown, one file per page. It is meant for AI tools. Start at markdown/index.md.

Introduction

Start here if you are new to git-nested.

• About git-nested

• Install git-nested

Quickstart

Try it out in a few minutes.

• git-nested in 5 minutes

• Everyday tasks

Concepts

The words git-nested uses, and how it works inside.

• Glossary

• How it works

• Compared to submodule and subtree

git nested command

The full reference of the command line. There is one page per command.

• Overview and common options

Command	What it does
clone	Copy an upstream repository into a folder
init	Turn a folder you have into a nested repository
pull	Get the new upstream changes
push	Send your changes upstream
fetch	Download upstream changes, change no file
status	Show all nested repositories
diff	Compare a nested repository with upstream
branch	Build a branch with the nested history
run	Run git in that branch’s worktree
commit	Add that branch back as one commit
repair	Fix the sync point after a squash merge
clean	Remove what git-nested left behind
config	Read or change .gitnested
completion	Print the shell completion script
version	Print the version

• Environment variables

Configuration

What git-nested stores, and where.

• The .gitnested file

• .gitnested examples

• git config settings

Guides

Step by step help for one task each.

• Resolve conflicts

• Nest only a part of upstream

• Pin a release

• Upstream submodules

• Adopt an existing folder

• Many nested repositories at once

• Squash merges and rebases

• Nested repositories inside nested repositories

• Hooks and signing

Architecture

How the code is built, and which git commands each command runs.

• Architecture

• Git call diagrams

Contributing

• Development

• Documentation