{"version":"2.1.227","anchor":"review-posting-consent-is-now-explained-as-one-shot","canonical_anchor":"review-posting-consent-is-now-explained-as-one-shot","heading":"Review posting consent is now explained as one-shot","tier":"notice","area":"Code Review","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/review-posting-consent-is-now-explained-as-one-shot","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Review posting consent is now explained as one-shot\n\nReview comment consent is now clearly one session only, and names what gets posted.\n\n**What**\n\nWhen a review runs with comment posting armed, the session message now says that the permission applies only to that session, and if the run fails the message states plainly that nothing was posted and nothing will be. The confirmation screen also names the GitHub account that would author the comment and notes that the comment carries a \"Generated by Claude Code\" line.\n\n**Evidence**\n\n`Nothing was posted to the pull request, and nothing will be \\u2014 the --post request ends with this run.`\n\n- Area: Code Review\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}