Blocking users from organizations via API doesn't allow to specify duration and other options

[nemesifier]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

API.

Related to github/roadmap#1284.

Body

The UI for blocking users allows specifying different options:

However, the REST API for blocking users does not allow specifying these options, it only allow supplying username and org.

In the age of AI, dealing with large quantities of sloppy PRs has become a serious issue. Open source projects are resource-constrained: whether we deal with PRs through human review or AI-assisted review, nobody is paying us to do it. If even a few users submit a large quantity of comments and PRs in a short period of time, they can quickly overwhelm maintainers and CI, consuming quotas or even paid CI/AI services.

Many projects have decided to close public contributions altogether or migrate to competing or self-hosted version control platforms.

In my case, I am trying a different approach: keeping contributions open while automatically detecting and flagging spammy contributions. There are recurring characteristics that make these contributions relatively easy to recognize, flag, and close.

However, even when the contributions are flagged and closed, some users persist in spamming. In my opinion, the only real solution is to temporarily block them for 1 to 7 days as a cool-down period, and send them a notification with instructions on how to contribute properly, submit quality work, and avoid overloading maintainers with low-quality contributions.

I have been doing this manually, and I am getting good results.

Please, GitHub, add the same blocking options available in the UI to the REST API.

[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. ⭐