{"version":"2.1.269","anchor":"pr-comment-posting-flow-reports-already-posted-vs-newly-post","canonical_anchor":"pr-comment-posting-flow-reports-already-posted-vs-newly-post","heading":"PR-comment posting flow reports already-posted vs newly-posted distinctly","tier":"notice","area":"Code Review","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/pr-comment-posting-flow-reports-already-posted-vs-newly-post","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### PR-comment posting flow reports already-posted vs newly-posted distinctly\n\nPosting review findings to a GitHub PR comment now reports whether the comment already existed or was just posted\n\n**What**\n\nWhen Claude Code posts ultrareview or code-review findings as a comment on a GitHub pull request, it now distinguishes two outcomes: a comment that already existed on the PR versus one that was just newly posted. Previously there was only a single 'posting' status paired with a session URL to follow along, with no separate 'already posted' case. The comment's URL is now always shown either way.\n\n**Why**\n\nThis avoids ambiguity about whether a new review comment was actually created or an existing one was found, and always giving the URL makes it easy to jump straight to the comment on GitHub.\n\n- Area: Code Review\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}