Issue

In Mendix Studio Pro 10.24.13, some Git commits may appear in the branch history without a Mendix Version or associated changes. Attempting to build an affected revision may result in an error, while subsequent commits may work as expected.

This issue can occur when Git outputs a warning related to an incorrectly configured safe.directory setting, which Studio Pro incorrectly interprets as commit metadata.

The Git logs shows the following warning logs 

2026-10-09 09:28:53.9077 TRACE Mendix.Modeler.VersionControl.Git.GitProcessRunner warning: safe.directory ''*'' not absolute

This article explains how to resolve the issue by upgrading Studio Pro and correcting the Git configuration.

Environment

Mendix Studio Pro 10.24.15 later

Cause

The Git configuration has a safe.directory value that is not an absolute path, because of this Git prints a warning safe.directory ''xx'' not absolute with every command it runs. Studio pro 10.24.13 could mistake that warning for the commit's metadata. The commit is then stored without it's Mendix version and change list, so history shows it as empty and it cannot be built.

Solution / Workaround

Following are the steps to resolve this issue:

• Upgrade Studio pro to the latest 10.24 patch (currently 10.24.28).

• Fix the Git config -  In Command Prompt run: 

  git config --global --unset-all safe.directory  

  Then add the add the actual app folders full path

  git config --global --add safe.directory "C:/Users/<user>/Mendix/<AppName>-main" 

• If the value was set in the system config instead, the same commands with --system apply.
• Run git status in an app folder, no not absolute warning should appear.