Update repository preferences for check suites should not be restricted to the GitHub App that created the check suite

[jackson-theisen]

Select Topic Area

Product Feedback

Body

The REST API endpoint for Update repository preferences for check suites is currently restricted to the GitHub App that created the check suite.

Attempting to modify this configuration via the API with a PAT results in a 403 error with message Invalid app_id 'xxxxxxx' - check suite can only be modified by the GitHub App that created it..

This option should be configurable by administrators (both via the API and repository settings in the browser) so the App behavior can be configured as desired out-of-the-box. With the current limitation, one has to create the App and hack together a way to make that initial API call on behalf of the App.

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