review-followup-example

Automate post-review follow-up verification by reading previous MR comments to identify blocking issues and checking if new commits address them, generating a concise report. This ensures fixes are complete and regressions are avoided before merging.

Yes, you can trigger automated follow-up validation in CI to verify code review fixes before merging. The process checks MR comments, diffs, and commits to confirm blocking issues are resolved and outputs a concise follow-up report.

Code review follow-up verification works with pull and merge request workflows on both GitHub and GitLab. It requires access to MR/PR comments, diffs, and commits to verify that blocking issues are addressed.

Verify new commits do not reintroduce problems by analyzing previous review comments and recent commit diffs to ensure blocking issues are addressed. The automated follow-up generates a report confirming fixes are complete and regressions are avoided.

Automating post-review follow-up reports requires access to pull request comments, diffs, and commits. This access allows the verification process to identify blocking issues and confirm they are resolved in the latest commits.