Duplicate reports/comments (potential issue)

[tmillr]

The same commit might get reported more than once (e.g. a tag gets pushed, the same commit is pushed to multiple branches, etc.).

It appears that a separate workflow run occurs for each pushed tag. I assume that the commits array of the event/webhook payload will be empty if the tagged commit already exists on GitHub? but not if gh does not already have the commit that the pushed tag points to? if this is the case, then it probably shouldn't be necessary to ignore pushed tags in hopes of avoiding duplicate reports due to breaking change seeing the same commit twice or more (once for the pushed commit workflow run, and once for each pushed tag that points to that commit).

Potential Fixes

• use a cache to note which commits have already been reported
• warn users of this in docs/readme
• investigate what happens when a tag gets pushed, how to avoid/ignore push events for tags