{"version":"2.1.287","anchor":"git-pushed-ancestor-lookup-returns-a-cause-with-a-headcommi","canonical_anchor":"git-pushed-ancestor-lookup-returns-a-cause-with-a-headcommi","heading":"Git push-state check now says why it could not tell","tier":"internal","area":"Git","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/git-pushed-ancestor-lookup-returns-a-cause-with-a-headcommi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Git push-state check now says why it could not tell\n\nWhen Claude Code cannot tell whether your git commits have been pushed, it now records a reason, and the check can take a specific commit\n\n**Unclear.** It is not clear whether these reasons are ever shown to the user.\n\n**What**\n\nClaude Code has a check that works out whether your git commits have been pushed to the remote repository. That check can now be pointed at a specific head commit (the latest commit on your branch). When it cannot reach an answer, it now gives a reason instead of a plain \"unknown\". The reasons include:\n\n- `nothing_vouched`\n\n- `not_a_commit_id`\n\n- `refspec_not_covering`\n\n- `git_failed`\n\n**Why**\n\nThis makes it easier to understand why Claude Code could not work out whether your work is pushed.\n\n- Area: Git\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}