{"version":"2.1.309","anchor":"git-commands-for-user-facing-status-run-with-the-users-loca","canonical_anchor":"git-commands-for-user-facing-status-run-with-the-users-loca","heading":"Some git commands now keep your own language settings","tier":"notice","area":"Git","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/git-commands-for-user-facing-status-run-with-the-users-loca","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Some git commands now keep your own language settings\n\nA new userLocale option lets git status, worktree lookups and a few other git calls run in your own locale instead of a forced one\n\n**What**\n\nClaude Code runs `git` in the background for many jobs. It builds a set of environment variables for each of these runs, and that set normally forces a fixed locale. A locale is the language and regional format a program uses for its messages. The builder now takes a `userLocale` option. When the option is not given, the fixed locale is still forced. When it is set (`userLocale: !0`), git keeps your own locale.\n\nThe git calls that now set it include:\n\n- `git status` (including `status --porcelain`)\n\n- the `rev-parse` call that finds the base of a worktree (a worktree is an extra checkout of the same repository in another folder)\n\n- a git call made when changes are not staged\n\n- one further git call\n\nThe same environment builder now also sets `GIT_NO_REPLACE_OBJECTS: \"1\"`.\n\n**Why**\n\nOutput from these git commands may now appear in your own language rather than the fixed one. If you read or rely on that output, expect its wording to follow your system's locale.\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}