This very post collects them as well, ironically (At least I cannot imagine how Hhhhhyy is advancing the discussion)
Questions to anyone interested in the matter:
Is this just a temporary thing, because maintainers are currently pretty busy with their private lives?
Are there any other solutions to get rid of them (the spammers, not the maintainers)?
Personally, I think it's annoying, unprofessional and worth a little effort to get rid of. What do others think?
Ideas:
AFAICT, @sindresorhus is lifting the whole weight alone at the moment.
Reading Github's guide on disruptive comments it says that write access or an organization is needed to moderate comments.
Maybe there is some person, @sindresorhus trusts enough and who has some time on their hands.
Alternatively, we could try to get obvious Spam reported. I tried with GitHub, but didn't seem to work. Maybe it works if more people report the same comment. Or, maybe it's an option to notify maintainers somehow.
Just some ideas, curious for feedback.
Originally created by @Mo-way on GitHub (Jul 13, 2025).
Original GitHub issue: https://github.com/sindresorhus/awesome/issues/3538
Currently, there are a lot of non-sense and spam comments in the PRs and Issues. For example:
- [Incubate](https://github.com/sindresorhus/awesome/issues/2242) issue is full of them.
- The [oldest one](https://github.com/sindresorhus/awesome/issues/2242#issuecomment-2552906489) is over half a year old.
- Table of content [issue](https://github.com/sindresorhus/awesome/issues/1972) has them as well
- [Web assmebly PR](https://github.com/sindresorhus/awesome/pull/3398) also has a bunch of spam comments.
- This very post collects them as well, ironically (At least I cannot imagine how `Hhhhhyy` is advancing the discussion)
Questions to anyone interested in the matter:
- Is this just a temporary thing, because maintainers are currently pretty busy with their private lives?
- Are there any other solutions to get rid of them (the spammers, not the maintainers)?
- Personally, I think it's annoying, unprofessional and worth a little effort to get rid of. What do others think?
Ideas:
AFAICT, @sindresorhus is lifting the whole weight alone at the moment.
Reading Github's guide on [disruptive comments](https://docs.github.com/en/communities/moderating-comments-and-conversations/managing-disruptive-comments) it says that write access or an organization is needed to moderate comments.
Maybe there is some person, @sindresorhus trusts enough and who has some time on their hands.
Alternatively, we could try to get obvious Spam reported. I tried with GitHub, but didn't seem to work. Maybe it works if more people report the same comment. Or, maybe it's an option to notify maintainers somehow.
Just some ideas, curious for feedback.
@PhillipBurtonIDoData commented on GitHub (Jul 30, 2025):
Maybe there should be a keyword to use, to indicate that an issue is Spam.
<!-- gh-comment-id:3136595054 -->
@PhillipBurtonIDoData commented on GitHub (Jul 30, 2025):
Maybe there should be a keyword to use, to indicate that an issue is Spam.
@Angel-Mathew007 commented on GitHub (Sep 4, 2025):
Hi!
I’m interested in contributing to this project and would like to help with this issue. Could you please provide some guidance on how best to proceed or assign it to me? I’m excited to contribute and learn.
Thank you!
<!-- gh-comment-id:3252618984 -->
@Angel-Mathew007 commented on GitHub (Sep 4, 2025):
Hi!
I’m interested in contributing to this project and would like to help with this issue. Could you please provide some guidance on how best to proceed or assign it to me? I’m excited to contribute and learn.
Thank you!
Hi @Angel-Mathew007 Why this project specifically? The maintainer is fairly busy & I have no idea how you can help. Feel free to come up with your own ideas.
<!-- gh-comment-id:3252805820 -->
@Mo-way commented on GitHub (Sep 4, 2025):
Hi @Angel-Mathew007 Why this project specifically? The maintainer is fairly busy & I have no idea how you can help. Feel free to come up with your own ideas.
One small thing that might help with reducing spam is adding structured issue/PR templates.
When contributors have to fill in specific fields (like description, steps)it makes random comments less likely.
<!-- gh-comment-id:3289276879 -->
@prriyayadav commented on GitHub (Sep 14, 2025):
One small thing that might help with reducing spam is adding structured issue/PR templates.
When contributors have to fill in specific fields (like description, steps)it makes random comments less likely.
@prriyayadav Good idea! Are there templates for comments as well? From my observation, Spam issues are quickly closed, but comments (see the ones above) stay forever
<!-- gh-comment-id:3301473377 -->
@Mo-way commented on GitHub (Sep 17, 2025):
@prriyayadav Good idea! Are there templates for comments as well? From my observation, Spam issues are quickly closed, but comments (see the ones above) stay forever
@jodikalin67-png commented on GitHub (Sep 20, 2025):
Hi my account are way messed up some one is using. Y accounts I need advice
<!-- gh-comment-id:3315108579 -->
@jodikalin67-png commented on GitHub (Sep 20, 2025):
Hi my account are way messed up some one is using. Y accounts I need advice
Those AI-generated 'reviews' need to be considered spam as well.
The guidelines already say that an Awesome List should be 'non-generated'. So I feel like comments should come under the same scrutiny.
Reviewing two lists is a requirement, and those AI-generated ones are not really reviews. They often point out issues that do not exist, and just repeat the guidelines.
I do not think mandating a template would help, as they take away creativity, the same way AI does.
Enforcing a minimum word limit might work, maybe. AFAIK GitHub does not natively support that.
I will not pinpoint specifics, but there are a few on my PR #3688. Hint: see comments of users whose names start with 'T'. There is one on this issue as well.
<!-- gh-comment-id:3648671071 -->
@hstsethi commented on GitHub (Dec 13, 2025):
Those AI-generated 'reviews' need to be considered spam as well.
The guidelines already say that an Awesome List should be 'non-generated'. So I feel like comments should come under the same scrutiny.
Reviewing two lists is a requirement, and those AI-generated ones are not really reviews. They often point out issues that do not exist, and just repeat the guidelines.
I do not think mandating a template would help, as they take away creativity, the same way AI does.
Enforcing a minimum word limit might work, maybe. AFAIK GitHub does not natively support that.
I will not pinpoint specifics, but there are a few on my PR #3688. Hint: see comments of users whose names start with 'T'. There is one on this issue as well.
I might be able to help u out as a newbie
Will do as you instruct just need some guidance from seniors about how everything works hope I will secure an opportunity to help😀
<!-- gh-comment-id:3873128122 -->
@STARKIO commented on GitHub (Feb 9, 2026):
I might be able to help u out as a newbie
Will do as you instruct just need some guidance from seniors about how everything works hope I will secure an opportunity to help😀
<!-- gh-comment-id:3876541779 -->
@aydenhailey78-hub commented on GitHub (Feb 10, 2026):
Keeping this for records
On Wed, Jan 14, 2026 at 2:29 AM Nani-ku ***@***.***> wrote:
> *natachanicolasmartinez-cmd* left a comment (sindresorhus/awesome#3538)
> <https://github.com/sindresorhus/awesome/issues/3538#issuecomment-3747379716>
>
> Tyr
> Fhhghl
> Gkliñoghlg
> Gfjoopff
>
> Jh:*((*(me and @Shahzad232 <https://github.com/Shahzad232> 847⚠️ＡＬＥＲＴＡ ＹＡ
> ＶＩＥＮＥＮ ＬＯＳ ＮＩÑＯＳ ＲＡＴＡＳ Ａ ＰＥＤＩＲ ＤＵＡ Ｙ ＮＯＶＩＡ ＣＯＰＩＥＮ Ｙ ＰＥＧＵＥ#p(_&+$*((200153)
> ⚠️ＡＬＥＲＴＡ ＹＡ⚠️ＡＬＥＲＴＡ🟥
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/sindresorhus/awesome/issues/3538#issuecomment-3747379716>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/B4CX3QANFXECAVOUX3I54VT4GWSXPAVCNFSM6AAAAACBNNJ3DWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTONBXGM3TSNZRGY>
> .
> You are receiving this because you are subscribed to this thread.Message
> ID: ***@***.***>
>
@Prathikgowda360 commented on GitHub (Mar 7, 2026):
Spam/Disruptive Comment Reporting Template
If you notice spam, off-topic, or disruptive comments in this repository, please help us report them politely and effectively.
How to Report
Locate the comment you believe is spam or disruptive.
Click the ... (three dots) next to the comment.
Select “Report content”.
Choose the most appropriate reason (usually “Spam” or “Harassment/abuse”).
Optional: Notify Maintainers
You can leave a brief comment on the issue or PR to notify maintainers, for example:
⚠️Spam alert: The following comment appears to be spam: [Insert link to comment or quote]
Multiple reports help GitHub review it faster.
Notes
Avoid engaging with spam comments directly. Responding can make them more visible.
Collective reporting is more effective — if several contributors report the same spam, GitHub is more likely to act.
If you have write access or are a trusted collaborator, you may hide the comment or lock the thread if appropriate.
Thank you for helping keep this community clean and professional! 🚀@prathikgowda360
<!-- gh-comment-id:4015906234 -->
@Prathikgowda360 commented on GitHub (Mar 7, 2026):
# Spam/Disruptive Comment Reporting Template
If you notice spam, off-topic, or disruptive comments in this repository, please help us report them politely and effectively.
---
## How to Report
1. **Locate the comment** you believe is spam or disruptive.
2. Click the `...` (three dots) next to the comment.
3. Select **“Report content”**.
4. Choose the most appropriate reason (usually **“Spam”** or **“Harassment/abuse”**).
---
## Optional: Notify Maintainers
You can leave a brief comment on the issue or PR to notify maintainers, for example:
> ⚠️ **Spam alert**: The following comment appears to be spam:
> `[Insert link to comment or quote]`
> Multiple reports help GitHub review it faster.
---
## Notes
- Avoid engaging with spam comments directly. Responding can make them more visible.
- Collective reporting is more effective — if several contributors report the same spam, GitHub is more likely to act.
- If you have write access or are a trusted collaborator, you may **hide the comment** or **lock the thread** if appropriate.
---
Thank you for helping keep this community clean and professional! 🚀@prathikgowda360
This very post collects them as well, ironically (At least I cannot imagine how Hhhhhyy is advancing the discussion)
Questions to anyone interested in the matter:
Is this just a temporary thing, because maintainers are currently pretty busy with their private lives?
Are there any other solutions to get rid of them (the spammers, not the maintainers)?
Personally, I think it's annoying, unprofessional and worth a little effort to get rid of. What do others think?
Ideas:
AFAICT, @sindresorhus is lifting the whole weight alone at the moment.
Reading Github's guide on disruptive comments it says that write access or an organization is needed to moderate comments.
Maybe there is some person, @sindresorhus trusts enough and who has some time on their hands.
Alternatively, we could try to get obvious Spam reported. I tried with GitHub, but didn't seem to work. Maybe it works if more people report the same comment. Or, maybe it's an option to notify maintainers somehow.
Just some ideas, curious for feedback.
Think we need to team up honestly
<!-- gh-comment-id:4211013797 -->
@earacicotjr-star commented on GitHub (Apr 9, 2026):
> Currently, there are a lot of non-sense and spam comments in the PRs and Issues. For example:
>
> - [Incubate](https://github.com/sindresorhus/awesome/issues/2242) issue is full of them.
> - The [oldest one](https://github.com/sindresorhus/awesome/issues/2242#issuecomment-2552906489) is over half a year old.
> - Table of content [issue](https://github.com/sindresorhus/awesome/issues/1972) has them as well
> - [Web assmebly PR](https://github.com/sindresorhus/awesome/pull/3398) also has a bunch of spam comments.
> - This very post collects them as well, ironically (At least I cannot imagine how `Hhhhhyy` is advancing the discussion)
>
> Questions to anyone interested in the matter:
> - Is this just a temporary thing, because maintainers are currently pretty busy with their private lives?
> - Are there any other solutions to get rid of them (the spammers, not the maintainers)?
> - Personally, I think it's annoying, unprofessional and worth a little effort to get rid of. What do others think?
>
> Ideas:
> AFAICT, @sindresorhus is lifting the whole weight alone at the moment.
> Reading Github's guide on [disruptive comments](https://docs.github.com/en/communities/moderating-comments-and-conversations/managing-disruptive-comments) it says that write access or an organization is needed to moderate comments.
> Maybe there is some person, @sindresorhus trusts enough and who has some time on their hands.
>
> Alternatively, we could try to get obvious Spam reported. I tried with GitHub, but didn't seem to work. Maybe it works if more people report the same comment. Or, maybe it's an option to notify maintainers somehow.
>
> Just some ideas, curious for feedback.
Think we need to team up honestly
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Mo-way on GitHub (Jul 13, 2025).
Original GitHub issue: https://github.com/sindresorhus/awesome/issues/3538
Currently, there are a lot of non-sense and spam comments in the PRs and Issues. For example:
Hhhhhyyis advancing the discussion)Questions to anyone interested in the matter:
Ideas:
AFAICT, @sindresorhus is lifting the whole weight alone at the moment.
Reading Github's guide on disruptive comments it says that write access or an organization is needed to moderate comments.
Maybe there is some person, @sindresorhus trusts enough and who has some time on their hands.
Alternatively, we could try to get obvious Spam reported. I tried with GitHub, but didn't seem to work. Maybe it works if more people report the same comment. Or, maybe it's an option to notify maintainers somehow.
Just some ideas, curious for feedback.
@qiunnley commented on GitHub (Jul 15, 2025):
Hhhhyy
@shoury222 commented on GitHub (Jul 19, 2025):
You should google it, my bro 😎
@PhillipBurtonIDoData commented on GitHub (Jul 30, 2025):
Maybe there should be a keyword to use, to indicate that an issue is Spam.
@NitinGangwal commented on GitHub (Aug 6, 2025):
I want to help you.
@Daddyyo22 commented on GitHub (Aug 14, 2025):
I can help out
@soyam99-max commented on GitHub (Aug 18, 2025):
Scams are prohibited
@Angel-Mathew007 commented on GitHub (Sep 4, 2025):
Hi!
I’m interested in contributing to this project and would like to help with this issue. Could you please provide some guidance on how best to proceed or assign it to me? I’m excited to contribute and learn.
Thank you!
@Mo-way commented on GitHub (Sep 4, 2025):
Hi @Angel-Mathew007 Why this project specifically? The maintainer is fairly busy & I have no idea how you can help. Feel free to come up with your own ideas.
@Shahzad232 commented on GitHub (Sep 4, 2025):
Maybe Scams
@adambhai commented on GitHub (Sep 8, 2025):
Testing
@prriyayadav commented on GitHub (Sep 14, 2025):
One small thing that might help with reducing spam is adding structured issue/PR templates.
When contributors have to fill in specific fields (like description, steps)it makes random comments less likely.
@Mo-way commented on GitHub (Sep 17, 2025):
@prriyayadav Good idea! Are there templates for comments as well? From my observation, Spam issues are quickly closed, but comments (see the ones above) stay forever
@jodikalin67-png commented on GitHub (Sep 20, 2025):
Hi my account are way messed up some one is using. Y accounts I need advice
@Shaurya-max76 commented on GitHub (Nov 13, 2025):
Listing the complete problem would have been better.
@hstsethi commented on GitHub (Dec 13, 2025):
Those AI-generated 'reviews' need to be considered spam as well.
The guidelines already say that an Awesome List should be 'non-generated'. So I feel like comments should come under the same scrutiny.
Reviewing two lists is a requirement, and those AI-generated ones are not really reviews. They often point out issues that do not exist, and just repeat the guidelines.
I do not think mandating a template would help, as they take away creativity, the same way AI does.
Enforcing a minimum word limit might work, maybe. AFAIK GitHub does not natively support that.
I will not pinpoint specifics, but there are a few on my PR #3688. Hint: see comments of users whose names start with 'T'. There is one on this issue as well.
@natachanicolasmartinez-cmd commented on GitHub (Jan 14, 2026):
Tyr
Fhhghl
Gkliñoghlg
Gfjoopff
Jh:(((me and @Shahzad232 847⚠️ＡＬＥＲＴＡ ＹＡ ＶＩＥＮＥＮ ＬＯＳ ＮＩÑＯＳ ＲＡＴＡＳ Ａ ＰＥＤＩＲ ＤＵＡ Ｙ ＮＯＶＩＡ ＣＯＰＩＥＮ Ｙ ＰＥＧＵＥ#p(_&+$*((200153)⚠️ＡＬＥＲＴＡ ＹＡ⚠️ＡＬＥＲＴＡ🟥
@cloodymood commented on GitHub (Jan 19, 2026):
It's good
@Jidedaizhijin commented on GitHub (Jan 24, 2026):
Good idea😄
@Jidedaizhijin commented on GitHub (Jan 24, 2026):
Good idea😄
@STARKIO commented on GitHub (Feb 9, 2026):
I might be able to help u out as a newbie
Will do as you instruct just need some guidance from seniors about how everything works hope I will secure an opportunity to help😀
@Mo-way commented on GitHub (Feb 10, 2026):
@STARKIO Sorry, but: did you even read the issue?
@sourav8423-sys commented on GitHub (Feb 10, 2026):
good
@aydenhailey78-hub commented on GitHub (Feb 10, 2026):
Keeping this for records
On Wed, Jan 14, 2026 at 2:29 AM Nani-ku @.***> wrote:
@Prathikgowda360 commented on GitHub (Mar 7, 2026):
Spam/Disruptive Comment Reporting Template
If you notice spam, off-topic, or disruptive comments in this repository, please help us report them politely and effectively.
How to Report
...(three dots) next to the comment.Optional: Notify Maintainers
You can leave a brief comment on the issue or PR to notify maintainers, for example:
Notes
Thank you for helping keep this community clean and professional! 🚀@prathikgowda360
@earacicotjr-star commented on GitHub (Apr 9, 2026):
Think we need to team up honestly
@armaansk2019-pixel commented on GitHub (Apr 16, 2026):
There are nonsense and rude comments coming