Revision number length differs between Studio Pro history and Team Server

Issue

In Mendix Studio Pro, the History tab displays revision identifiers using a shortened Git commit hash. The revision hash shown in Studio Pro contains 7 characters, while the corresponding revision displayed in Team Server contains 8 characters. This behavior can appear inconsistent, as the final character shown in Team Server is not visible in Studio Pro.

Environment

• Mendix Portal
• Studio Pro (all versions)
• Version Control

Cause

This behavior is caused by differences in how Git commit hashes are represented.

Studio Pro relies on Git’s default abbreviated commit hash functionality. Git automatically determines the minimum number of characters required to uniquely identify a commit within the repository. In many repositories, 7 characters are sufficient, which is why Studio Pro commonly displays 7-character hashes.

If uniqueness cannot be guaranteed with 7 characters, Git automatically increases the length of the abbreviated hash as needed.

Team Server, on the other hand, displays commit hashes using a fixed length of 8 characters. This is a presentation choice and does not affect the underlying commit identifier.

Solution/Workaround

No change is planned for this behavior.

Studio Pro intentionally follows Git’s default behavior for abbreviated commit hashes to ensure that the displayed hash is always uniquely identifiable within the repository. Hardcoding the display length to 8 characters could create situations where it could be assumed that exactly 8 characters are always sufficient for unique identification, which is not guaranteed in all repositories.

Therefore, the current Studio Pro implementation is working as designed.

Additional information

Not applicable