SocketDev / SocketDev/socket-cli
GitHub App: PR overview comment re-edited on every push with no content change
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 317
- Forks
- 65
- Avg merge
- 1h 26m
- Merged PRs (30d)
- 30
Description
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the GitHub App's PR overview comment rendering and update path, then compare the rendered body with the existing comment while ignoring scan-run IDs in dashboard URLs. Done means pushes with an unchanged dependency diff leave the comment untouched and avoid duplicate notifications and issue_comment.edited webhooks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100