[Feature Request] Add an option to disable emoji reactions for a repository

[slarticodefast]

Select Topic Area

Product Feedback

Body

I am a maintainer for a larger open source computer game. We have many players who take part in discussions on pull requests adding new features. Sadly these can often become non-constructive or even outright toxic, in particular 👎 reactions on the PRs are used as a cheap way to show disagreement.

• Downvotes are used instead of giving actual constructive feedback to the author.
• 👍 and 👎 are used as a kind of poll for each PR, giving the wrong impression that features are merged based on popularity alone, rather than what is reviewed and accepted conceptually by maintainers.
• It can be frustrating for PR authors to be downvoted after putting effort into contributing, creating a bad environment in our community.

To fix this I would request a setting that allows us to disable all emoji reactions on our repository.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[LukasBel]

Not a permanent solution for works temporarily

1. Navigate to your repository on GitHub.com

2. Click on "Settings" in the top navigation bar of your repository

3. In the left sidebar, select "Moderation options"

4. Click on "Interaction limits"

5. Choose the type of limit you want to apply:

   "Limit to existing users" (restricts new accounts less than 24 hours old)
   "Limit to prior contributors" (restricts users who haven't contributed before)
   "Limit to repository collaborators" (most restrictive option)

6. Select a duration for the limit:

   24 hours
   3 days
   1 week
   1 month
   6 months

7. Click "Save" to apply the interaction limits

This will restrict users from adding emoji reactions based on the limit type you selected. The restriction will automatically expire after the chosen duration.

[slarticodefast]

We tried this out before, the problem is that setting this to prior contributors only means that non-contributors won't be able to open new issues and cannot comment at all. Since we want anyone to be able to make bug reports this is not an option for us.
It would be great if these restrictions would be split up by interaction type.

[shinybrightstar]

Welcome to the GitHub Community, @slarticodefast , we're happy you're here! You are more likely to get a useful response if you are posting your question(s) in the applicable category. Check out this Guide on how to post in the right category. It'll ensure your questions and discussions reach the right people faster!

This particular discussion belongs in the Repositories category, I've gone ahead and moved it for you. Good luck!