{"version":"2.1.317","anchor":"git-guidance-wording-for-remote-environments","canonical_anchor":"git-guidance-wording-for-remote-environments","heading":"Remote sessions now commit and push only if the project folder is a git checkout","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/git-guidance-wording-for-remote-environments","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Remote sessions now commit and push only if the project folder is a git checkout\n\nIn remote environments, Claude is now told to commit or push on the other machine only if the project folder there is a git checkout\n\n**What**\n\nWhen Claude Code works in a remote environment, it gives Claude instructions about where the project really lives. Claude used to be told that the project's real checkout is on that machine, and that commits and pushes should happen there. It is now told that the project's real copy is on that machine, and to commit or push there only if that folder is a git checkout. A git checkout is a folder tracked by the git version control tool.\n\n**Why**\n\nThis changes what Claude is told to do in remote environments. It no longer assumes the remote folder is under git, so it should not try to commit or push in a folder that is not tracked by git.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}