{"version":"2.1.233","anchor":"repo-metadata-distinguishes-gitlab-and-bitbucket","canonical_anchor":"repo-metadata-distinguishes-gitlab-and-bitbucket","heading":"Repo metadata distinguishes GitLab and Bitbucket","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233\/e\/repo-metadata-distinguishes-gitlab-and-bitbucket","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233","markdown":"### Repo metadata distinguishes GitLab and Bitbucket\n\nYour repo's host is now recorded as GitLab or Bitbucket by name instead of one catch-all label.\n\n**What**\n\nA new classifier maps a git remote's host to \"github\", \"gitlab\", \"bitbucket\" or \"other\", so repo metadata that previously recorded one lumped \"non_github_host\" now names GitLab and Bitbucket separately. A companion helper pulls the hostname out of both SSH-style and URL-style remotes.\n\n**Evidence**\n\n`bitbucket.org`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}