{"version":"2.1.259","anchor":"git-operation-telemetry-extended-to-gitlab-merge-requests","canonical_anchor":"git-operation-telemetry-extended-to-gitlab-merge-requests","heading":"Git operation telemetry extended to GitLab merge requests","tier":"internal","area":"Git Integration","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259\/e\/git-operation-telemetry-extended-to-gitlab-merge-requests","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259","markdown":"### Git operation telemetry extended to GitLab merge requests\n\nCreating a GitLab merge request now counts toward the same PR-created telemetry as a pull request.\n\nThe git-command telemetry and PR-tracking logic, which already detects `gh pr create` and pushes, now also matches merge-request creation patterns via a second matcher alongside the existing pull-request one. Creating a GitLab merge request increments the same PR-created counter used for pull requests, and pushed-branch PR links are now tracked even without an existing `gh pr view` match.\n\n- Area: Git Integration\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}