GitHub user xuang7 added a comment to the discussion: Stuck merge queue postmortem
I agree that we need an emergency path. With the merge queue as the only way to merge changes and nobody able to bypass it, a period of runner unavailability could block the entire project. Having no fallback doesn't seem ideal. Some background on the earlier attempt Yicong mentioned: During my v1.2 release manager assignment, #5354 and #5413 added my account as a bypass actor in the Default Branch Protection ruleset. I could create branches as usual, but I still couldn't delete a protected release branch. While this doesn't necessarily mean the bypass configuration wasn't applied, it does raise some questions about how the permissions actually work. Before deciding who should have bypass privileges, I think it would be worth asking an admin to confirm that bypass_actors in .asf.yaml are actually being applied, and then testing the bypass with a harmless PR. GitHub link: https://github.com/apache/texera/discussions/9104#discussioncomment-19341752 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
