{"version":"2.1.315","anchor":"git-remote-error-message-changed","canonical_anchor":"git-remote-error-message-changed","heading":"Missing-GitHub-remote errors share one hint that suggests git remote add","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/git-remote-error-message-changed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Missing-GitHub-remote errors share one hint that suggests git remote add\n\nErrors about a missing GitHub remote in ultrareview and cloud agents now share one hint, which covers a GitHub repo that already exists\n\n**What**\n\nSome Claude Code features need your project to be linked to a GitHub repository, called a remote. When there is no such link, they show an error. The advice in those errors changed:\n\n- The \"needs a GitHub remote\" errors now use a shared hint. Before, the advice was written into each error: run `gh repo create --source=. --push` to create the repository. These errors include the one ending \"so it can clone this repository into the cloud\" and the one ending \"so it knows which repository the PR is in\".\n\n- The shared hint ends with: \"If a GitHub repo already exists, run `git remote add origin REPO_URL && git push -u origin HEAD`.\"\n\n- The cloud agents `no_git_remote` message now has the same hint added.\n\n**Why**\n\nUltrareview and cloud agents now give the same advice. That advice also covers a project whose GitHub repository already exists but is not linked to it yet.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}