{"version":"2.1.248","anchor":"fewer-git-calls-when-the-working-tree-is-already-up-to-date","canonical_anchor":"fewer-git-calls-when-the-working-tree-is-already-up-to-date","heading":"Fewer git calls when the working tree is already up to date","tier":"notice","area":"Git Integration","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/fewer-git-calls-when-the-working-tree-is-already-up-to-date","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Fewer git calls when the working tree is already up to date\n\nFewer git processes run per turn when your working tree hasn't changed.\n\n**What**\n\nThe working-tree sync step now compares the two trees first and skips the git read-tree call entirely when they match, and checks the index for changes before deciding whether a refresh is needed. Fewer git processes per turn on unchanged checkouts.\n\n**Evidence**\n\n`--ignore-submodules=none`\n\n- Area: Git Integration\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}