GitHub ruleset bypass only works when rule is in "Evaluate" mode #153705
Replies: 1 comment
|
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Uh oh!
There was an error while loading. Please reload this page.
Select Topic Area
Question
Body
I'm trying to set up a github branch ruleset to require approval of pull releases before merging. But I want an exception for our automated release action. I thought I had it working with the ruleset in "evaluate" mode, but when I make the ruleset "active", it fails. What's the correct way?
I've set up the action to use a token associated with a bot that I've put on the rule's bypass list.
When the rule is in "evaluate" status, it works fine. The pull requests generated by the action don't require approval and merge fine. There is an entry in the insights for the rule that marks the action as "bypass". That's exactly what I want.
But when I change the rule to "active", the pull requests require approval again.
Isn't the point of the "evaluate" status to check how the rule would perform when active?
This also holds true when I include "repository admins" in the bypass rules. Then, when the rule is under "evaluate" status, I, the repository creator, can make PRs that don't need approvals. When the rule is "active", I can't.
What is actually required to allow a contributor to be exempt from a requirement of pull request approvals?
(My only hesitance on reporting this as a bug, is that my organization maybe has additional rules I can't see, but that wouldn't explain why the "evaluate" mode works as expected, and I can't see how there would be a rule to modify my rule only when "active" in a way that's not visible.)
All reactions