codecov-commenter is spamming six-year-old closed PRs

Open
#917 3 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Domain
ci-cd

Research direction

Review the six linked pull-request comments and the Codecov commenter behavior described in the issue. Done means comments stop appearing on closed PRs in the old repository without preventing valid comments on newer PRs; the issue notes that the reporter lacks repository admin access.

Written by the indexing model from the issue text.

Description

Waiting for: Product Owner

For the past two months, I'm getting a drip-feed of @codecov-commenter comments on PRs that were closed six years ago. For example:

This is very spammy and not very helpful.

I'm maintaining this project in another repo (https://github.com/python-humanize/humanize) and don't have admin access to the old repo to change any hooks or so on (otherwise I wouldn't have needed to move repos in the first place).

Please can you disable it?

Otherwise my options appear to be:

  • Wait for codecov-commenter to comment on every closed PR...
  • Stop watching the old repo. Then I can't help any humans there.
  • Block the codecov-commenter account from my personal account
    • Then at least it cannot "Comment on or edit issues or pull requests that you've created"
    • This might prevent its valid comments on newer PRs.

Thank you!

Originally posted by @hugovk in #497

Dominant language
No language data
Stars
52
Forks
25
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from codecov/feedback

All issues in codecov/feedback

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.