Back to guides

Git configuration in apps-cli

Git configuration in apps-cli

This guide explains how to configure Git integration in apps-cli, including one-time setup, typical workflows, and troubleshooting.

GitLab preset

Host: gl.nimbusweb.co

Group: vibecode

Access token

Open token settings in GitLab

Scopes: api, read_api, read_repository, write_repository, read_registry, write_registry

1) One-time setup

  • Enable global flags like and in interactive mode via .
  • Authenticate in the target environment ( or ) so GitLab sync resolves to the correct namespace.
  • Use this preset in .
    Create the token here with scopes:
  • During configuration, CLI suggests a repository name and you can edit it if needed. Example: .

2) Supported scenarios

  • New app + Git + Sync: Run to initialize local git, set origin, and push in one flow.
  • Existing project without git: Run , then .
  • Already have local git without sync: Run to keep local history and attach/push remote.

3) Core commands

fusebase config flags

Open interactive flag setup (`git-init`, `git-debug-commits`).

fusebase config gitlab

Configure GitLab integration parameters (host, group, token).

fusebase init

Create a new app and run the git flow using your current config.

fusebase git

Initialize local git in an existing project.

fusebase git sync

Create/connect remote repository and push the current branch.

fusebase git sync --git-tag-managed

Run sync and apply the managed tag in GitLab.