Avoid posting comment multiple times in same PR

[florisvdg]

The fact that the PR comment gets posted on every push if there's 1 (older) commit in the PR that's unsigned can result in noisy PRs.

So instead of posting the PR comment over and over, we'll now check the PR comments and only post the comment if it hasn't been posted earlier. This won't impact the exit code that gets returned.

Resolves #8

Logs of test runs can be found here: unsigned commit that results in comment and second unsigned commit that skips the comment.

[kdheepak]

Can I check on the status of this PR? Friendly bump!

[edif2008]

Thank you for improving the experience. This looks great to me. I do appreciate you providing logs for tests runs showing how this adjustment positively impacts the action.

I have one question (non-blocking). From my understanding, the comment message isn't updated if it already exists. However, how can a user who adds more commits to a PR know that the specific comment is still up-to-date and relevant? Having the pipeline fail is one way to achieve it, but is this enough? 🤔

Approved. ✅ 💪🏻

[florisvdg]

However, how can a user who adds more commits to a PR know that the specific comment is still up-to-date and relevant? Having the pipeline fail is one way to achieve it, but is this enough?

That's a bit of a trade-off, indeed. But the first comment is already so in your face that I think having the check fail will later on will be enough.