This topic describes problems that you can encounter when you connect a Reltio tenant to Git, connect to a Git repository, work with branches, and upgrade a workspace. A failed Reltio tenant connection appears as Failed to connect tenant to Git: reason, where the reason states the cause.

Git asks for a password or a push fails

Error: could not read Username for …, or a push that fails and asks for a password.

What this error means

Git cannot sign in to your Git host to read from or push to the remote Git repository.

Why the error occurs

Git is not signed in to your Git host on this computer. The integrated development experience uses your existing Git sign-in and does not store credentials.

How to fix the issue

1. Sign in to your Git host through your credential manager or the command-line tool of your host.

2. Publish the branch again from the Source Control view.

A branch is created locally but not published

Error: Branch "name" was created locally but could not be published: reason or Branch "name" was created locally but could not be pushed: reason

What this error means

The branch exists on your computer, but the integrated development experience could not push it to your remote Git repository.

Why the error occurs

The push failed, usually because Git is not signed in to your Git host or because of a network problem. The reason in the message states the cause.

How to fix the issue

1. Fix the cause. For a sign-in problem, see Git asks for a password or a push fails. For a network problem, check your connection.

2. Publish the branch from the Source Control view.

Git executable is not found

Error: Git executable not found. Install Git (https://git-scm.com/downloads) and ensure it is on your PATH, then try again.

What this error means

The integrated development experience cannot start Git.

Why the error occurs

Git is not installed, or its location is not on the system path of your computer.

How to fix the issue

1. Install Git from git-scm.com/downloads, and make sure that Git is on your system path.

2. If Git is installed in another location, set the git.path setting in Cursor or VS Code to the location of the Git executable.

3. Close and reopen the editor.

4. Run git --version in a terminal to confirm that Git starts.

5. Connect to Git again.

A Git operation times out

Error: Git operation timed out after 5 minutes. Check your network connection and git credentials, then try again.

What this error means

A Git operation did not finish within 5 minutes.

Why the error occurs

The connection to your Git host is slow or unavailable, or Git is waiting for credentials.

How to fix the issue

1. Check your network connection.

2. Confirm that Git is signed in to your Git host.

3. Try the operation again.

Switching branches is blocked

Error: This tenant has uncommitted changes. Commit or stash them before switching to "branch".

What this error means

The integrated development experience did not switch the Reltio tenant to the branch you selected.

Why the error occurs

Switching branches replaces the files in the tenant folder with the files of the other branch, so the integrated development experience does not switch while the Reltio tenant has uncommitted changes.

How to fix the issue

1. In the Source Control view, commit or stash your changes.

2. Switch to the branch again.

Preventive measures

To keep your changes while you start new work, create a new branch instead. A new branch takes your uncommitted changes with it.

A tenant is skipped during the workspace upgrade

Error: The upgrade notification lists a Reltio tenant as skipped, and Show details states that the tenant folder has uncommitted Git changes.

What this error means

The integrated development experience did not move the Reltio tenant to the current folder layout.

Why the error occurs

The tenant folder is a Git repository with uncommitted changes. The upgrade skips it so that your work is not mixed into the move.

How to fix the issue

1. Commit or discard the uncommitted changes in the tenant folder.

2. Reopen the workspace. The upgrade runs again for the Reltio tenant.

Restore the earlier folder layout

Situation: You need the folder layout that your workspace had before the upgrade, for example to work with a colleague who has not updated the integrated development experience.

Background

The upgrade moved the files of each Reltio tenant to the current folder layout. The upgrade saved a backup of each tenant folder in .reltio-ide-backup at the top of your workspace.

How to fix the issue

1. Open the Command Palette. Press Ctrl+Shift+P on Windows and Linux, or Cmd+Shift+P on macOS.

2. Run Undo Layout Migration.

3. In the dialog box, select Restore.

The integrated development experience restores each Reltio tenant from the backup and lists the Reltio tenants that it restored. The folder names stay as the upgrade renamed them. The upgrade runs again the next time you open the workspace.

Tenant files appear in another Git repository

Error: A warning states A Git repository exists at … and offers Ignore Tenant Folders, Show Details, and Don't Show Again.

What this error means

The workspace folder or one of its parent folders is already a Git repository. This outer Git repository tracks your Reltio tenant files, or, for a Reltio tenant that is connected to Git, records only a reference to a commit. A clone of the outer Git repository then has an empty tenant folder, and the paths in the outer Git repository include your environment and tenant names.

How to fix the issue

1. In the warning, select Ignore Tenant Folders. The integrated development experience adds your environment folders to the .gitignore file of the outer Git repository.

2. To stop the outer Git repository from tracking files that it already tracks, run git rm -r --cached environment-folder in the outer Git repository, and then commit the change.

Preventive measures

To keep each Reltio tenant in its own Git repository, do not use a workspace folder that is inside another Git repository. Select Show Details in the warning for an explanation of your options. Select Don't Show Again if you keep the whole workspace in one Git repository on purpose.