codecov-commenter is spamming six-year-old closed PRs
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
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:
- https://github.com/jmoiron/humanize/pull/171#issuecomment-3833007524
- https://github.com/jmoiron/humanize/pull/125#issuecomment-3867777810
- https://github.com/jmoiron/humanize/pull/124#issuecomment-4161912309
- https://github.com/jmoiron/humanize/pull/122#issuecomment-4181011070
- https://github.com/jmoiron/humanize/pull/127#issuecomment-4182206558
- https://github.com/jmoiron/humanize/pull/121#issuecomment-4191189715
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
- 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.
More from codecov/feedback
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Bundle analysis: `normalizePath` replaces everything after the first `-` in a file name, so different assets collidePossibly taken @ChiptenIsCool claimed this 16 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Docs Waiting for: Product Owner
Difficulty 1/5 Under an hour Newbie friendliness 65/100
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
-
Difficulty 4/5 1-2 days Newbie friendliness 42/100
All issues in codecov/feedback
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
nutmos/expensetrackr#157 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
janitor-team/janitor#2613 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
keyxmakerx/Chronicle#2550 ·
Maintainers usually reply within 1 day
-
ci/cd javascript medium sdk
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
bug good first issue help wanted rust type:infrastructure
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Open-Glassbeetle/glassbeetle#374 ·
Maintainers usually reply within 1 day