post-code-review-to-pr

You can automate posting code review results to a GitHub pull request by executing a full review and using scripts to publish the findings directly as PR comments or formal reviews.

The best way to format code review findings is to build a review body from standard sections like Review Summary and Findings by severity, applying a post-processing clarity check to refine wording before posting.

Yes, you need the gh CLI installed to post PR comments and reviews to GitHub. The automation requires gh to coordinate with metadata scripts and publish the final review body.

Yes, you can post a formal GitHub review instead of a comment. The posting method depends on the author and user context, utilizing dedicated scripts for either formal reviews or standard PR comments.

Retrieving pull request metadata involves using a dedicated pr-metadata script within the workflow. This gathers the necessary PR context to properly craft and target the code review results before posting.

A limitation is that the review body must be read from a temporary file before posting, and the workflow requires both gh and jq dependencies to properly parse metadata and execute the posting scripts.