Quick configuration

Git Town prompts for all the configuration information it needs. The commands below set additional configuration options that might be helpful in your use case. We will cover the full list of options later.

Shorter commands

Having to type git town <command> gets old. Git Town can install aliases for its commands that make them feel like native Git commands, i.e. allow you to run for example git hack instead of git town hack. To enable this feature:

git town aliases add

To remove these aliases, run git town aliases remove.

API access to your hosting provider

Git Town can ship branches that have an open pull request by merging this pull request via your code hosting service's API. To enable it, create an API token for your account at your code hosting provider.

• instructions for GitHub
• instructions for GitLab
• instructions for Gitea

Provide the token to Git Town as an environment variable with name GITHUB_TOKEN or GITHUB_AUTH_TOKEN or as part of the Git Town configuration:

• GitHub:

  git config --add git-town.github-token <your api token>
  

• GitLab:

  git config --add git-town.gitlab-token <your api token>
  

Delete remote branches

Some code hosting providers automatically delete feature branches after merging them. This is a useful feature that you should enable if possible. It can interfere with Git Town's attempts to also delete this branch after shipping it. To make Git Town play along, run:

git config git-town.ship-delete-remote-branch false

Shell autocompletion

Follow the instructions given by git-town help completions to install the autocompletions for your shell.