---
title: "Comment by Rishabh Mishra on \"Design a review queue before enabling automatic actions\" | Hashnode"
description: "The post-approval edit test is the part I'd stress most. In practice, the approval should bind to a specific draft version, so any change after approval sends t"
url: "https://hashnode.com/posts/design-a-review-queue-before-enabling-automatic-actions/6affb4b0db353eccccccc3b1/comment/6affb86b8df888972ef1d3eb"
---

[Discussion](https://hashnode.com/posts/design-a-review-queue-before-enabling-automatic-actions/6affb4b0db353eccccccc3b1)

Comment [Design a review queue before enabling automatic actions](https://hashnode.com/posts/design-a-review-queue-before-enabling-automatic-actions/6affb4b0db353eccccccc3b1)

[Rishabh Mishra](https://hashnode.com/@rushdeploy)

[2d ago](https://hashnode.com/posts/design-a-review-queue-before-enabling-automatic-actions/6affb4b0db353eccccccc3b1/comment/6affb86b8df888972ef1d3eb)

The post-approval edit test is the part I'd stress most. In practice, the approval should bind to a specific draft version, so any change after approval sends the item back to NEEDS\_REVIEW automatically. Otherwise the queue quietly becomes a rubber stamp.
