Urgent Security Feature Request: Ability to require MFA confirmation ("sudo") for elevated "bypass" actions.

[aaronsteers]

Select Topic Area

Product Feedback

Body

As we increasingly use bots for coding, we need to have confidence that certain actions are performed by a human. The best way to do this as of now is to require MFA confirmation for elevated tasks. This is already happening today for certain actions such as updating security group memberships and adding new GitHub Apps to an organization.

The most important action I think we need to enable is that organizations should be able to require MFA for administrators to force-merge a pull request. Today there is a toggle "Use your administrative permissions to..." And I suggest that organizations should be able to opt in to also require MFA for this action.

Administrators are often staff engineers or engineering managers - they need the ability to have a force-merge ability, but they also will be actively testing new coding bots - both locally on their machine (like codex CLI), and remotely with hosted agents (like GitHub Copilot).

Basically: any time a branch protection or other repo protection is bypassed, it should require elevation/confirmation of identity via MFA. This would go a long way to give companies confidence that risk is mitigated - and that a rogue (or misguided) agent would not be able to bypass branch protections.

🙏 Thank you for your consideration!

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