Branch Protection - do not allow anyone to push straight to protected branch but allow admins to bypass PR review req

[mollypi]

Select Topic Area

Question

Body

Hi - I was wondering if there is a way to allow individuals on a repo to bypass the pull request review requirement while at the same time do not allow them to push straight to a protected branch

I noticed the - Do not allow bypassing the above settings](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches#do-not-allow-bypassing-the-above-settings)

but obviously that enforces everything to not be bypassed

thanks!

[sarathkumar-s]

you can use the option Allow specified actors to bypass required pull requests under settings -> branches -> select the branch -> edit and add the people who are admin or you can add people as a group.

[mollypi]

I dont want them to be able to bypass a pull request - ONLY be able to bypass the review requirement. is that possible?

[RuhchaiHo]

It will still fail if the repo has any status checks with the setting on 'Do not allow bypassing the above settings'.

[LyleDavis]

I’m very surprised this isn’t a feature already. If using a git repo to control your deployments, you need the ability for certain people to be able to force-merge a pull request for emergencies without allowing those people to accidentally git push to the branch that is used to deploy from.

[maxisam]

ah....and it doesn't work if the last commit is a auto fix from a bot and doesn't provide any status check or go thru any check.

[niij]

@dannyskoog those steps work for me to block pushes to main from git, while still allowing bypass in the UI. Thank you!

[Horytnik]

For me @dannyskoog steps don't work. In our project sometimes status checks stuck (due to our platform reasons) and in this case we need to just bypass pull request but if all status checks are not finished it is still not possible and we need to disable "do not allow bypassing the above settings". Does anyone knows other solution?

[dannyskoog]

For me @dannyskoog steps don't work. In our project sometimes status checks stuck (due to our platform reasons) and in this case we need to just bypass pull request but if all status checks are not finished it is still not possible and we need to disable "do not allow bypassing the above settings". Does anyone knows other solution?

When the status checks get stuck, have you tried cancelling them to see if you can merge after that?

[lkchava]

@maxisam Were you able to find a solution to bypass the status check. We needed this when we make a automated merge to main to bump the release version.

[github-actions[bot]]

🕒 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 out of date at the bottom of the page.

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 Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬