Delegated bypass for branch rulesets #188670
Replies: 1 comment
-
|
💬 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.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Product Feedback
Body
The delegated bypass feature currently available for push rulesets (as detailed in Managing code rulesets) is awesome. It provides a bypass mechanism that is both asynchronous and fully traceable.
However, this functionality is currently missing for branch rulesets. At present, branch rules only support direct bypass. This creates two significant pain points:
Bringing the delegated bypass workflow to branch rulesets would allow for a "request-and-approve" model directly within the PR UI, ensuring all exceptions are documented and approved by the right people without leaving the platform.
Are there any plans to roll out delegated bypass for branch rulesets in the near future?
Beta Was this translation helpful? Give feedback.
All reactions