{"version":"2.1.248","anchor":"github-failures-now-name-the-actual-problem","canonical_anchor":"github-failures-now-name-the-actual-problem","heading":"GitHub failures now name the actual problem","tier":"notice","area":"GitHub","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/github-failures-now-name-the-actual-problem","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### GitHub failures now name the actual problem\n\nGitHub failures now say whether you're not connected or the repo wasn't found.\n\n**What**\n\nA new classifier turns a raw HTTP failure into a specific cause: a 401 with an auth-required error becomes \"not connected\", a 404 with a missing-resource error becomes \"repo not found\", and anything else stays inconclusive so the old generic message is used.\n\n**Details**\n\n- The two named verdicts are what let the review preflight print tailored guidance rather than a status code.\n\n**Evidence**\n\n`github_repo_not_found`\n\n- Area: GitHub\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}