# GitHub merge queue w/ Netlify **URL:** \ **Category:** Support\ **Tags:** deployment, github-actions\ **Created:** [May 16, 2023, 6:59pm UTC](https://answers.netlify.com/t/github-merge-queue-w-netlify/92522 "2023-05-16T18:59:22Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![arcanis](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/arcanis/32/50890_2.png) [@arcanis](https://answers.netlify.com/u/arcanis)\ **Post date:** [May 16, 2023, 6:59pm UTC](https://answers.netlify.com/t/github-merge-queue-w-netlify/92522/1 "2023-05-16T18:59:22Z")
I have a little issue with [https://yarnpkg.com](https://yarnpkg.com/). I’m trying to enable the [GitHub merge queue](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue#triggering-merge-group-checks-with-github-actions), but the required Netlify status never passes, and thus the PRs can’t be merged: ![image](https://global.discourse-cdn.com/netlify/original/3X/2/0/2031b506e2184028e4617c42df005ce17ba025cc.png) I can’t tell Netlify to run on the merge queue branch, because GitHub creates them on the fly with variable names. For example: [gh-readonly-queue/master/pr-5447-(hash)](https://github.com/yarnpkg/berry/tree/gh-readonly-queue/master/pr-5447-2ebfd213c462456e92b704b06a69e0328e6c08f2). At the moment the only solution I can find is to make the Netlify job non-required. ---
**Author:** ![hrishikesh](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/hrishikesh/32/74607_2.png) [@hrishikesh](https://answers.netlify.com/u/hrishikesh)\ **Post date:** [May 21, 2023, 5:48pm UTC](https://answers.netlify.com/t/github-merge-queue-w-netlify/92522/2 "2023-05-21T17:48:39Z")
Hi @arcanis, At the moment, I don’t see a way to trigger a Netlify check for a Merge Queue. So this would most likely be a feature request, which I don’t know if/when it will be worked on. So it seems like you might have to go with the optional way. I’ll still run this by the devs to see if this is something that can be easily supported (or a workaround). ---
**Author:** ![hrishikesh](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/hrishikesh/32/74607_2.png) [@hrishikesh](https://answers.netlify.com/u/hrishikesh)\ **Post date:** [May 24, 2023, 11:25am UTC](https://answers.netlify.com/t/github-merge-queue-w-netlify/92522/4 "2023-05-24T11:25:18Z")
As confirmed with the dev team, we don’t support first class. As a workaround, you can enable the site to build all branches and that should unblock it, but might cause more builds than you’d like. You also might have to create a build plugin or a shell script to exit early on non-merge-queue builds to save some time. ---
**Author:** ![andrew.walker](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/andrew.walker/32/51401_2.png) [@andrew.walker](https://answers.netlify.com/u/andrew.walker)\ **Post date:** [March 11, 2024, 3:30pm UTC](https://answers.netlify.com/t/github-merge-queue-w-netlify/92522/5 "2024-03-11T15:30:47Z")
We would also love merge queue support in Netlify. So just want to +1 this feature request. ---
**Author:** ![marcus.little](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/marcus.little/32/49084_2.png) [@marcus.little](https://answers.netlify.com/u/marcus.little)\ **Post date:** [March 13, 2024, 3:07pm UTC](https://answers.netlify.com/t/github-merge-queue-w-netlify/92522/6 "2024-03-13T15:07:38Z")
Hi Andrew, Thanks for getting in touch and letting us know! I’ve added you to the existing feature request. We still don’t have a timeline for when this might be implemented, but we’ll be sure to follow up here with any updates on progress. ---
**Author:** ![steveoh](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/steveoh/32/59744_2.png) [@steveoh](https://answers.netlify.com/u/steveoh)\ **Post date:** [March 21, 2024, 4:06pm UTC](https://answers.netlify.com/t/github-merge-queue-w-netlify/92522/7 "2024-03-21T16:06:07Z")
I am also interested in this feature. Add me to the feature request please! ---
**Author:** ![SamO](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/samo/32/41847_2.png) [@SamO](https://answers.netlify.com/u/SamO)\ **Post date:** [March 22, 2024, 1:07pm UTC](https://answers.netlify.com/t/github-merge-queue-w-netlify/92522/8 "2024-03-22T13:07:47Z")
Thanks for shaing your feedback steve! ---
**Author:** ![avdv](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/avdv/32/77554_2.png) [@avdv](https://answers.netlify.com/u/avdv)\ **Post date:** [September 28, 2026, 7:57am UTC](https://answers.netlify.com/t/github-merge-queue-w-netlify/92522/9 "2026-09-28T07:57:44Z")
Hey! I am also interested in seeing proper support for deployments with Github’s merge queue. Any update on this? What’s the best way to workaround these days?