UnityRef is currently in early development. Some features may be incomplete and/or not functioning.

UNITYREF

Your Pit Stop For Solving ANYTHING in Unity

assets

[Version Control] Locating Local Repository Paths on macOS

Solution

version controlmacosgitstoragedeveloper workflow

Unity 2021.x - Unity 6.3.x

Published 10 days ago

Author Profile Photo

Reviewed by _architect

Chief Editor

80 posts
Issue

 The physical filesystem location for Unity Version Control or Git repositories on macOS is not explicitly displayed within the Unity Editor, complicating manual file operations or external tool integration.

Quick-Fix

The RepositoryPath for local assets is generally stored within the user directory or a hidden folder at the root of the project structure.

Expand Analysis

To identify the RepositoryPath on macOS systems, direct filesystem navigation or command-line queries are required.

  1. For Git-based projects, open the Terminal and navigate to your project directory.
  2. Execute the command git rev-parse --show-toplevel to retrieve the absolute RepositoryPath.
  3. For Unity Version Control (Plastic SCM) metadata, navigate to the hidden folder located at /Users/[user]/.plastic4 to access client-side configuration.
  4. To toggle visibility of hidden files like .git or .plastic4 in Finder, use the keyboard shortcut Cmd + Shift + ..

Additional Tips:

  • Ensure the Unity Editor is closed before manually modifying files within the RepositoryPath to prevent database conflicts.
  • The default RepositoryPath for projects cloned via the Unity Hub is typically found in the ~/Unity Projects folder unless customized during the initial clone process.

Related Posts Haven't quite found a solution to your problem? We think these posts might help you.
[PlasticSCM] Master Distributed Workflows: Project Collaboration Unlocked[Version Control] Xlink Check-in Fails Across Different Repositories[Hub] Unlock Download Management: Pause & Resume Editor Installs

Content inspired by a Unity discussion post.