{"version":"2.1.248","anchor":"running-an-upload-outside-a-git-repo-is-reported-as-its-own-","canonical_anchor":"running-an-upload-outside-a-git-repo-is-reported-as-its-own-","heading":"Running an upload outside a git repo is reported as its own failure","tier":"internal","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/running-an-upload-outside-a-git-repo-is-reported-as-its-own-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Running an upload outside a git repo is reported as its own failure\n\nUploading from a non-git directory is now reported distinctly instead of as an empty repo.\n\n**What**\n\nStarting a repository upload from a directory that is not a git repo used to be recorded as an empty repo. It now reports a distinct `not_a_repo` reason, so the two situations can be told apart.\n\n**Details**\n\n- The new outcome appears in the returned `failReason` and in both the analytics event and the bundle-upload event.\n\n**Evidence**\n\n`teleport_git_bundle_upload`\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}