Merge queue setting not available #56838
Replies: 4 comments
-
|
I could use this as well. |
Beta Was this translation helpful? Give feedback.
-
|
Also can't see the merge queue configuration in my branch protection settings, and i don't understand why... |
Beta Was this translation helpful? Give feedback.
-
|
I was having the same issue. Found this in the docs:
Is this causing your issue? It was the case for me since we use a private organization repository, but are only on the Teams plan. |
Beta Was this translation helpful? Give feedback.
-
|
🕒 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! 💬 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Question
Body
I'm looking to try out merge queues for one of my organization's public repositories: https://github.com/vaadin/flow-components.
According to the docs, the repository should be applicable for using merge request queues (is public, is in an organization), however the
Require merge queuesetting does not show up in the branch protection rules. The only other restriction I could find is that wildcards are not allowed in the branch pattern, which is not the case for us.What am I missing?
Beta Was this translation helpful? Give feedback.
All reactions