The Socket GitHub App's PR overview comment (<!-- overview-comment -->) is edited in place after every push, even when the dependency diff is completely unchanged. On one PR I observed 8 edits in ~50 minutes; diffing the bodies, the only change each time was the diff-scan/<uuid> in the dashboard links — same package, same scores, same table, byte-identical otherwise.
Each edit re-notifies subscribers and fires issue_comment.edited webhooks, so unchanged scans produce pure notification churn for humans and bots watching the PR.
Request: skip the comment edit when the rendered body (ignoring scan-run IDs in URLs) is identical to what is already posted. The new scan ID doesn't need to reach the comment — the dashboard already has it
The Socket GitHub App's PR overview comment (
<!-- overview-comment -->) is edited in place after every push, even when the dependency diff is completely unchanged. On one PR I observed 8 edits in ~50 minutes; diffing the bodies, the only change each time was thediff-scan/<uuid>in the dashboard links — same package, same scores, same table, byte-identical otherwise.Each edit re-notifies subscribers and fires
issue_comment.editedwebhooks, so unchanged scans produce pure notification churn for humans and bots watching the PR.Request: skip the comment edit when the rendered body (ignoring scan-run IDs in URLs) is identical to what is already posted. The new scan ID doesn't need to reach the comment — the dashboard already has it