Can not create a Branch protection rule

[mburton-crawfordtech]

Select Topic Area

Question

Body

I am trying to enforce pull requests and want to create a Branch protection rule to prevent pushing to the main branch.
For a repository, I got the Settings -> Branches. Click :Add branch protection rule" Enter main for the Branch name pattern (that is the main default branch). Check "Require a pull request before merging"
Pressing the "Create" button at the bottom does nothing. No error, nothing.

I have tried this with both Free public and and private Teams repositories.

[nigerninja]

Weird, I am here because I am having the exact same issue trying to create a Branch Protection Rule. No errors, no message, just depresses the button and no further response.

[jeff-young-deltatre]

yup, same problem here

[sdake]

Please note in the repo https://github.com/xertai/sdac, my main branch was locked, probably by my error. I couldn't remove the locked branch protection rule, so I deleted it.

The XertAI is a paid-seat organization.

I am now unable to create a new branch protection rule for main. I have tried every option on and off, no joy. I have then deleted any and nearly all limitations on the repository - making the org and repo wide open, also no joy...

Feels like a recent defect introduction?

Thank you.
-steve

[sdake]

I would like to add, this problem applies to all repos within the https://github.com/xertai org. Specifically, https://github.com/xertai/community.

[sdake]

#44526

[sdake]

I would encourage others suffering from this problem to create a github ticket and link this public issue.

https://support.github.com/tickets/personal/0

[jeff-young-deltatre]

Update: I cleared

• local storage
• session storage
• cookies

and the problem resolved

[fei-rakkar]

Tried after clearing all cache, local storage, etc and also incognito mode. The problem still persists.

Even tried it on different browsers with zero histories, cache, etc. NO luck

Logged a case in https://support.github.com/tickets/personal/0

[tgip-work]

After clearing browser data, I was able to create a branch protection rule. But afterwards I could not change an existing rule.
So, problem still persists

[HerbertScroggins]

I would add that I am able to create a rule... but only if no restrictions are selected - pretty pointless rules therefore.

[darostegui]

As a workaround, apparently emptying the cache and hard reloading resolves the issue. In Google Chrome, you can do shift+command+R (Ctrl and press F5 on windows) to “hard” reload, which should force the browser to reload cached resources. If you have dev tools open, you can also right-click on the refresh button, and it’ll have a button to “Empty cache and hard reload.”

Also, you can use the REST API to create a branch protection rule.

[HerbertScroggins]

While not ideal, that worked for me. Cheers

[HerbertScroggins]

Also worth noting that, before doing the hard reload, the footer of the page doesn't appear, the page stops at the button. After the hard reload, the entire page including the footer appears.

[MrFlish]

I found a workaroud
after editing my ruless, i rewrote the name of my branch and the create button did work again.

[jcw1031]

I'm having the same problem :(

[Dancho80]

same issue for me, on several repos

[mburton-crawfordtech]

I also filed a bug report with GitHub. Turns out there was a defect that they have since fixed.
It it working for me now.
Thanks to the GitHub eng team for the quick fix!

[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! 💬