{"version":"2.1.301","anchor":"git-named-remote-that-is-a-group-is-refused-for-retry","canonical_anchor":"git-named-remote-that-is-a-group-is-refused-for-retry","heading":"Claude Code won't retry when a git remote name refers to a group of remotes","tier":"notice","area":"Git","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/git-named-remote-that-is-a-group-is-refused-for-retry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Claude Code won't retry when a git remote name refers to a group of remotes\n\nIf a git remote name is defined as a group of remotes, Claude Code now reports that and does not retry\n\n**What**\n\nGit lets you group several remotes under one name with a `remotes.<name>` entry in git config. A remote is a copy of the repository somewhere else, such as on GitHub. When the remote name Claude Code is given is defined as one of these groups, Claude Code now returns a result marked as not worth retrying.\n\n**Why**\n\nThis covers an unusual setup where a remote name is actually a group of remotes.\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}