{"version":"2.1.299","anchor":"pushed-ancestor-git-check-deadline-depends-on-a-setting","canonical_anchor":"pushed-ancestor-git-check-deadline-depends-on-a-setting","heading":"Time limit for checking pushed commits now depends on a setting","tier":"internal","area":"Git","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/pushed-ancestor-git-check-deadline-depends-on-a-setting","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Time limit for checking pushed commits now depends on a setting\n\nThe time limit for Claude Code's check of which commits are already pushed now picks between two values depending on a setting\n\n**Unclear.** It is not clear which setting chooses the time limit or whether you can change it.\n\n**What**\n\nClaude Code runs a Git check to find which of your commits have already been pushed, meaning sent to a shared remote copy of the repository. The time it allows that check used to be one fixed value. It is now one of two values, chosen by whether a setting is \"on\".\n\n**Why**\n\nThe time the check is given can now differ from one setup to another.\n\n- Area: Git\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}