Problems Using "Bypass Branch Protections" in Organization Roles #166649
-
Select Topic AreaBug BodyHi, I've been attempting to make use of the Organization Roles feature to simplify some bypass lists in various organization-level rulesets. I've noticed that the "Bypass branch protections" and "Push commits to protected branches" permissions of the repository settings in Organization Roles seem to have no effect - any users we assign this role are still required to be present on the bypass list for a ruleset or their pushes to a protected branch are denied. I'm not sure if I'm missing a setting, misunderstanding the feature or there's a bug here. Any help would be much appreciated. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
|
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
Beta Was this translation helpful? Give feedback.
-
|
What the This is an opportunity to be more clear and I'm going to look into our documentation to update this! |
Beta Was this translation helpful? Give feedback.
What the
Bypass Branch Protectionsdoes is allow a user to be in the "admin" list when bypass is enabled for classic branch protections. It has no effect on rulesets.This is an opportunity to be more clear and I'm going to look into our documentation to update this!