git town prepend

git town prepend [<branch-name>...] [-b | --beam] [--body <string>] [--propose] [-p | --prototype] [-t <text> | --title <text>] [-d | --detached] [-c | --commit] [-m | --message <message>] [--dry-run] [-v | --verbose]

The prepend command creates a new feature branch as the parent of the current branch. It does that by inserting the new feature branch between the current feature branch and it’s existing parent.

Consider this stack:

main
 \
* feature-2

We are on the feature-2 branch. After running git town prepend feature-1, our repository has this stack:

main
 \
* feature-1
   \
    feature-2

If your Git workspace is clean (no uncommitted changes), it also syncs the current feature branch to ensure you work on top of the current state of the repository. If the workspace is not clean (contains uncommitted changes), git town prepend does not perform this sync to let you commit your open changes.

If the branch you call this command from has a proposal, this command updates it. To do so, it pushes the new branch.

Options

--body <string>

Pre-populate the body of the pull request to create with the given text. Requires --propose.

--propose

Propose the created branch.

To always propose new branches, set the share new branches setting to propose.

-p
--prototype

Adding the --prototype aka -p switch creates a prototype branch.

-t <text>
--title <text>

Pre-populate the title of the pull request to create with the given text. Requires --propose.

-d
--detached

The --detached aka -d flag does not pull updates from the main or perennial branch. This allows you to build out your stack and decide when to pull in changes from other developers.

-c
--commit

When given, commits the currently staged changes into the branch to create and remains on the current branch. This is intended to quickly commit changes unrelated to the current branch into another branch and keep hacking on the current branch. Committing suppresses all branch updates to allow you to get your open changes committed.

-b
--beam

Moves (“beams”) one or more commits from the current branch to the new parent branch that gets created. Lets you select the commits to beam via a visual dialog. Beaming suppresses all branch updates. Any merge conflicts encountered while beaming arise from moving the beamed commits.

-m
--message

Commit message to use together with --commit. Implies --commit.

--dry-run

Use the --dry-run flag to test-drive this command. It prints the Git commands that would be run but doesn’t execute them.

-v
--verbose

The --verbose aka -v flag prints all Git commands run under the hood to determine the repository state.

Configuration

If share-new-branches is configured, git town hack creates a remote tracking branch for the new feature branch. This behavior is disabled by default to make git town hack run fast. The first run of git town sync will create the remote tracking branch.

If the configuration setting new-branch-type is set, git town prepend creates a branch with the given type.