-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integration with GitHub merge-queue #366
Comments
Hi @yanns, thanks for raising this. The GitHub merge queue functionality is currently in beta, I see, and the beta was announced less than a month ago. In GitHub's documentation for the feature they say:
That being the case, I'm minded to wait until the feature is more stable before working on a potential solution, if that sounds reasonable? It sounds to me like the issues you have outlined are fairly generic to the new merge queue functionality rather than specific to the label checker, so I'm thinking there is a reasonable chance that GitHub will provide a more generic solution in the coming months 🤞🏻 Let me know what you think, thanks |
👍 |
OK I found a way to make it work. I hope this can help others.
Explanations:
|
When using GitHub merge-queue, GitHub creates new branch for merging pull requests.
This brings two issues.
First, the label checker is running only on pull requests:
The documentation specifies the trigger as follow:
This can be fixed by adding this trigger:
Second, even if we run the label checker on those branches to be merged, we have an issue as they are no pull requests for them, and no labels. The check fails with the error message:
What can we do?
Maybe we can detect if the action is run for a branch for the merge-queue, and always succeed in that case?
The text was updated successfully, but these errors were encountered: