Requesting comments on *Posting a welcome comment before closing a spam pull request*

[IamLizu]

I believe that when closing a spam pull request, we can drop a comment that informs the OP about how they should engage in the project in case they want.

I think it creates a sort of better welcoming behavior and possibly helps getting a traction of collaborators / contributors.

Please review my proposed comment, I will post it in another comment so that the rendering can be viewed.

## 🌟 Welcome to the Express.js GitHub Repository! 🌟

Hello, and thank you for your interest in contributing to Express.js! We appreciate your enthusiasm and would love to guide you on how to make meaningful contributions to our project. Here are some ways you can get involved:

### 📚 Read the Contribution Guidelines
Before you start, please take a moment to read our [Contribution Guidelines](https://github.com/expressjs/express/blob/master/Contributing.md). This document contains important information on how to contribute effectively.

### 🐛 Report Bugs
If you've found a bug, great! Head over to our [Issues page](https://github.com/expressjs/express/issues) and open a new issue. Please provide as much detail as possible so we can understand and address the problem quickly.

### 💡 Suggest Features
Got an idea for a new feature? We'd love to hear it! Open a feature request in the [Issues page](https://github.com/expressjs/express/issues) and explain your idea. Your suggestions help us make Express.js even better.

### 🔨 Submit Pull Requests
Ready to code? Fantastic! Before you submit a pull request, make sure to check our [Pull Request Guidelines](https://github.com/expressjs/express/blob/master/Contributing.md#pull-requests). Ensure your changes align with our coding standards and include tests if applicable.

### 📖 Improve Documentation
Good documentation is essential. If you spot a typo or think something could be clearer, please submit a pull request with your improvements. Every little bit helps!

### 🤝 Join the Discussion
Engage with the community by participating in discussions on existing issues or pull requests. Your insights and feedback are invaluable.

Thank you for considering contributing to Express.js. We believe that everyone can make a positive impact, and we look forward to your contributions!

Happy coding! 🚀

[IamLizu]

🌟 Welcome to the Express.js GitHub Repository! 🌟

Hello, and thank you for your interest in contributing to Express.js! We appreciate your enthusiasm and would love to guide you on how to make meaningful contributions to our project. Here are some ways you can get involved:

📚 Read the Contribution Guidelines

Before you start, please take a moment to read our Contribution Guidelines. This document contains important information on how to contribute effectively.

🐛 Report Bugs

If you've found a bug, great! Head over to our Issues page and open a new issue. Please provide as much detail as possible so we can understand and address the problem quickly.

💡 Suggest Features

Got an idea for a new feature? We'd love to hear it! Open a feature request in the Issues page and explain your idea. Your suggestions help us make Express.js even better.

🔨 Submit Pull Requests

Ready to code? Fantastic! Before you submit a pull request, make sure to check our Pull Request Guidelines. Ensure your changes align with our coding standards and include tests if applicable.

📖 Improve Documentation

Good documentation is essential. If you spot a typo or think something could be clearer, please submit a pull request with your improvements. Every little bit helps!

🤝 Join the Discussion

Engage with the community by participating in discussions on existing issues or pull requests. Your insights and feedback are invaluable.

Thank you for considering contributing to Express.js. We believe that everyone can make a positive impact, and we look forward to your contributions!

Happy coding! 🚀

[IamLizu]

I posted this in #5771 as a trial :)

[wesleytodd]

I would love to hear other folks input on this, but IMO whatever folks can do to help reduce the burden of these spam PRs would be awesome as long as it doesn't block real progress or add too much complexity. This approach seems good to me in those regards. Our current approach is to lock the issues as spam, and there are not enough volume to make it more than an annoyance. Honestly it would have been really nice to see that YT channel take down or edit their video because it has been an issue for about a year now and Github has been very little help (they did clean out the spam PRs once for us, but that requires us contacting support which is just another thing on the ever growing todo list).

[cipherswami]

@wesleytodd
I guessing you guys are aware of the "Update README.md" spams are because of Apna College YT video, Why don't you guys put a request to take down the video from YT.

[jackwellerreal]

Or even trying to get the creator to remove the section of the video that tells people to do it.