Skip to main content

Git Configuration

Anchorpoint reads Git-related settings from the project's .ap/config.ini file. These settings control file locking behavior, branch unlock rules, and file history options.

Git username and email​

Anchorpoint sets the author of your Git commits in the following order:

  1. If user.name and user.email are set in the local Git config, those values are used.
  2. Otherwise, your Anchorpoint account name and email are used.
  3. You can force a custom identity at any time under Account Settings → Git → Commit Author Settings by enabling Custom E-Mail and/or Custom Username.

Configuration file​

All settings are placed under the [git] section of your project's .ap/config.ini:

[git]
no_lock_paths = content/*, art/
no_unlock_branches = fix/*, release/*
auto_lock_new_files = true
file_history_follow = true
file_history_rename_threshold = 50
cross_branch_lookback_days = 7

Settings​

no_lock_paths​

A comma-separated list of wildcard patterns for paths where automatic file locking is disabled.

Pattern rules:

  • content/ — matches files directly inside content/ (one level only)
  • content/* — matches all files inside content/ recursively

Example:

no_lock_paths = content/*, art/

no_unlock_branches​

A comma-separated list of wildcard patterns for branches where automatic unlock after push is disabled. This is useful for release or protected branches where locks should persist.

Pattern rules:

  • release/ — matches branches directly under release/ (one level only)
  • release/* — matches all branches under release/ recursively

Example:

no_unlock_branches = fix/*, release/*

auto_lock_new_files​

When set to true, new (untracked) files are automatically locked when added.

Default: false

auto_lock_new_files = true

file_history_follow​

When set to true, file history uses Git's --follow flag to track files across renames.

Default: true

file_history_follow = true

file_history_rename_threshold​

Controls the rename detection threshold for file history. Accepts a value between 0 and 100. A lower value means Git considers files as renamed even with more changes; a higher value requires closer similarity.

Default: not set (uses Git's default)

file_history_rename_threshold = 50

cross_branch_lookback_days​

The number of days to look back when checking for file changes across branches.

Default: 7

cross_branch_lookback_days = 7