Configure Git Behavior

Objective

Establish the requested Git behavior at the narrowest valid scope while preserving unrelated configuration and revealing provenance.

Use When

• Set or diagnose author/committer identity, signing, pull/rebase defaults, default branch, diff/merge drivers, aliases, or credential helpers.
• Maintain .gitignore, .gitattributes, repository-owned hooks, or config includes.
• Explain why local, worktree, global, system, conditional include, or environment configuration wins.
• Configure safe line-ending, filemode, case, symlink, or long-path behavior with platform evidence.

Do Not Use / Route Elsewhere

• Use manage-remotes for remote URLs and refspecs.
• Use manage-large-files for LFS tracking and large-object policy.
• Use craft-commits to create commits or choose commit-message style.
• Do not place credentials or tokens in config.