{"version":"2.1.227","anchor":"remote-review-stops-early-on-a-repository-with-no-commits","canonical_anchor":"remote-review-stops-early-on-a-repository-with-no-commits","heading":"Remote review stops early on a repository with no commits","tier":"notice","area":"Code Review","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/remote-review-stops-early-on-a-repository-with-no-commits","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Remote review stops early on a repository with no commits\n\nRemote review on an empty repository fails fast with a clear reason instead of hanging on.\n\n**What**\n\nBefore starting a remote review, Claude Code now checks whether the repository has any refs at all and fails the precondition with reason `no_refs`, instead of continuing into a merge-base calculation that could never succeed.\n\n**Details**\n\n- The check runs `git for-each-ref --count=1 refs\/`.\n\n**Evidence**\n\n`\"for-each-ref\", \"--count=1\", \"refs\/\"`\n\n- Area: Code Review\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}