When a commit which has the "Relates-To" tag is created, the bot will add the "ready for review" label to the related issue. However when the commit is merged, the bot doesn't remove the label. This causes a problem when a GH issue requires multiple commits to close, since the first commit marks it as "ready to review", and merging that commit doesn't remove the label, leaving the issue labeled "ready to review" with no changes to review.
A solution might involve checking whether there are any "Relates-To" or "Closes" commits that are not closed, and if so, label the issue. Otherwise, verify that the issue is not labeled.
Adding some context.
When a commit which has the "Relates-To" tag is created, the bot will add the "ready for review" label to the related issue. However when the commit is merged, the bot doesn't remove the label. This causes a problem when a GH issue requires multiple commits to close, since the first commit marks it as "ready to review", and merging that commit doesn't remove the label, leaving the issue labeled "ready to review" with no changes to review.
A solution might involve checking whether there are any "Relates-To" or "Closes" commits that are not closed, and if so, label the issue. Otherwise, verify that the issue is not labeled.