{"version":"2.1.274","anchor":"git-repository-access-errors-are-now-classified-into-denial","canonical_anchor":"git-repository-access-errors-are-now-classified-into-denial","heading":"Git repository access errors are now classified into denial reasons","tier":"notice","area":"Git","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/git-repository-access-errors-are-now-classified-into-denial","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Git repository access errors are now classified into denial reasons\n\nGit access failures during clone\/fetch are now classified into specific denial reasons\n\n**What**\n\nWhen a git command fails while cloning or fetching a repository (for example, for git-backed connectors), Claude Code now matches the failure's error text against known patterns and classifies it as one of: `repo_not_found_or_no_permission`, `no_credentials`, `authentication_failed`, or `blocked_by_git_proxy`. This is attached to a new `RepositoryAccessError`.\n\n**Why**\n\nClassifying git failures this way means error handling and user-facing messages can be more specific about why access failed, instead of showing a generic git error.\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}