{"version":"2.1.257","anchor":"reviews-comment-flag-can-post-findings-to-gitlab-mrs","canonical_anchor":"reviews-comment-flag-can-post-findings-to-gitlab-mrs","heading":"\/review's --comment flag can post findings to GitLab MRs","tier":"use","area":"Code Review","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/reviews-comment-flag-can-post-findings-to-gitlab-mrs","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### \/review's --comment flag can post findings to GitLab MRs\n\n\/review --comment can now post its findings as a general note on a GitLab merge request via glab.\n\n`\/review`'s `--comment` flag now works against GitLab merge requests: when the target is a GitLab MR, findings are posted as a single general MR note via `glab mr note ... -m \"<body>\"`, falling back to printing the findings if `glab` isn't available or the target isn't an MR. The `--comment`\/`--post` explanation text now branches by target, describing GitHub inline PR comments separately from the GitLab general MR note behavior.\n\n- Area: Code Review\n- Names: `\/review`, `--post`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 2\/5"}