Git settings#
You can customize how Git behaves in Anchorpoint. There are global and project based settings which you can change.
Workspace Settings#
These settings are available under “Workspace Settings” / “Git” and are applied for all projects.
Show Notifications for new Commits#
As soon as Anchorpoint detects new commits on your Git server, you will receive a push notification.
Disable Git Safe Directory Check#
Off by default. Disabling Git’s safe directory check is a security risk because it allows Git to operate in directories not owned by you. In multi-user environments—such as university computer labs or shared Windows systems—malicious users can place a .git directory in a commonly writable location (like /scratch/ or C:\) to exploit Git behavior. Simply navigating into such a directory can compromise your account if Git is triggered (e.g., through a Git-enabled prompt). The safe directory check prevents this by ensuring Git only trusts repositories in directories you own. Disabling it removes this protection and exposes you to potential privilege escalation attacks.
Auto Lock Deleted Files#
Anchorpoint can automatically lock files that are deleted or renamed in the Git repository, if Auto Locking is enabled in the Project Settings. This prevents other users from modifying these files until you push them to the Git repository.
This option has no effect if Auto Locking is disabled in the Project Settings.
Default Commit Operation#
This sets the default operation when committing changes. If set to Sync, Anchorpoint will automatically push and pull changes after committing. If set to Commit, you will need to manually push and pull changes.
Clear Git File Cache automatically#
The Git LFS stores committed files in a cache under the .git folder. This cache grows as your commit history grows. Anchorpoint can automatically clean it up, saving you disk space.
Open Git Console/ Terminal#
Allows you to open the Git command line. This version of Git is also set up correctly, uses Anchorpoint’s version of Git LFS and also uses the shared Git configuration parameters (see below).
Edit Git config#
The Git config allows you to adjust the parameters of how Git behaves by default. You often tweak it when something is not working the way you want it to. But when you have a team of 50 people, tweaking everyone’s Git config can be daunting. That’s why Anchorpoint allows you do add shared Git config parameters that are automatically applied to every Anchorpoint user in your workspace.
Say you’re using a self-hosted Git server, and you need to adjust the postbuffer because large pushes don’t work out of the box. If you add this parameter to Anchropoint’s shared Git config, it will automatically be applied to everyone else.
In general it’s recommended to test parameters locally before you add them to the shared Anchorpoint Git config. Parameter that are setup in the Anchorpoint Git config, will override the local Git config file.
Note on Git hooks For example, if you want to set a custom hooks path using the centralized git config, you need to follow the instructions in the Git documentation, such as “core.hooksPath” as the key and then your directory as the value.
Project Settings#
These settings are available under “Project Settings/ Git”.
Repository URL#
Shows the remote URL. Normally you don’t need to change that.
Create .gitkeep files in new folders#
By default, Git does not understand empty folders. If you e.g. want to create a folder structure with empty folders in a Git repository, Anchorpoint will add a hidden .gitkeep file so they can be uploaded to Git.
Automatically track all binary files as LFS#
Anchorpoint creates the .gitattributes file automatically by adding all binary files which it detects in a commit. If you want to modify this file manually, disable the option.
Auto Lock Binary Files#
This will automatically lock all modified or deleted binary files. When you rename a binary file or folder containing them, Git will show these files as deleted and added. The deleted files will be locked. If Anchorpoint detects any deleted files, a pop-up will ask if you want to lock them.
Using the Unreal Engine plugin will disable this option automatically, because locking will be controlled via the plugin.
Auto Lock Text Files#
Anchorpoint locks binary files by default because they cannot be merged. Text files can be merged, so locking is generally not necessary. However, there are some exceptions when it comes to complex document files, such as .unity or .ma (Maya ASCI) files that were edited by the application rather than a text editor. It often makes sense to lock them, because merging them would be extremely difficult in case of conflicts.
Disable on Branches#
The “Disable on Branches” feature allows you to prevent auto-locking from triggering on specific branches. By configuring patterns such as release/*, you can exclude.
Open Git Console/ Terminal#
Opens a command line application, so you can use any Git commands. This is more suited for programmers or debugging purposes.
Clear Cache#
This will delete old versions from your hard drive, but not from the server, to free up space on your computer. It will only remove cached files that have already been pushed to your Git server. It will never remove local commits that have not yet been pushed.
This command is called “LFS prune” in Git parlance, and cleans up the entire LFS cache. Anchorpoint also does this automatically based on an interval set in “Workspace Settings” / “Git”. Per default it’s removing cache files older than one week.
Update Credentials#
Opens the login interface where you authorize Anchorpoint with the Git hosting provider (GitHub, GitLab, Azure DevOps etc.). This is useful when you e.g. changed your account.
Refresh Sparse Checkout#
If you see incorrect states in the tree view in the right pane of the Explorer (e.g., wrong cloud icon), you can update the selective checkout index so that Anchorpoint scans all files that have been checked out to show the correct state.