AllowForcePushes returns "false" when "Allow force pushes" is checked and bypassForcePushAllowances is used

[briansearles-an]

Select Topic Area

Bug

Body

I am attempting to use the GraphQL API to enumerate Branch Protection Rules across a large number of organizations and repositories. I am seeing an unexpected result from AllowForcePushes (boolean) when any user is enabled under "Specify who can force push", showing within the result for bypassForcePushAllowances (object containing actors). In this condition, the UI does also show "Allow force pushes" to be ticked, which is the main point of concern.

Expected: AllowForcePushes returns true if "Allow force pushes" is ticked under any circumstances, including when any user is allowed within "Specify who can force push"

Actual: AllowForcePushes returns false unless "Everyone" is selected.

Here is a current configuration to demonstrate the discrepancy, along with the resulting response recorded using the GraphQL explorer:

While possible to work around by accounting for the return within bypassForcePushAllowances, this seems like an oversight and it would be far cleaner for AllowForcePushes to represent the overall status of the Branch Protection Rule.

Open to feedback or corrections if I am going about this incorrectly in any way.

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