Set up configuration

If your repository already contains a .git-town.toml or .git-branches.toml file, you’re all set. If not - or if something isn’t working as expected - Git Town provides an interactive that guides you through the entire configuration process. Just run:

git town config setup

This command walks you through all available configuration options, explains what each one does, lets you adjust them, and validates that everything is working correctly.

For more details on how Git Town handles configuration, see the configuration reference.

API access

Some Git Town features require access the your code forge. This allows Git Town to:

• infer the parent of a branch from open pull requests
• automatically update pull requests when you prepend, rename, or remove branches or change their parent
• trigger pull request merges directly from your terminal

Configuring API access is straightforward. Git Town supports the following platforms:

• GitHub: uses the GitHub CLI. If you prefer not to install gh, you can also configure an access token and use Git Town’s built-in GitHub integration.
• GitLab: uses the GitLab CLI. Without glab, you can configure an access token for Git Town’s built-in GitLab support.
• Bitbucket: requires a username and app password
• Gitea: requires an access token
• Codeberg: requires an access token