-
Notifications
You must be signed in to change notification settings - Fork 736
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
Pull request mergeability is boolean but should be trinary #275
Comments
And while you will calculate single variable you can:
All code that i know care about status themselve. |
And btw, that what i wrote to GH API developers about, but didn't get any answer. |
I'm not sure I follow? I ended up chasing this down because Jenkins thought every commit it saw was unmergeable and refused to build them, when in actuality it just didn't know whether or not it could be merged. Seems like letting the API say "null" instead of coercing the 3 possible inputs to 2 outputs lets people downstream do the right thing |
This the library and it returns what gh API provides. API provides 3 states, everything right. |
This library correctly defines @PerilousApricot it seems to me that you should be actually filing this bug to whatever Jenkins plugin that takes this |
@kohshuke I have the utmost respect for you. I was using Jenkins before it With the 2.0 push, isn't the point to make the common case easier? GitHub On Friday, June 3, 2016, Kohsuke Kawaguchi [email protected] wrote:
It's dark in this basement. |
According to the API docs:
"The value of the mergeable attribute can be true, false, or null. If the value is null, this means that the mergeability hasn't been computed yet, and a background job was started to compute it. Give the job a few moments to complete, and then submit the request again. When the job is complete, the response will include a non-null value for the mergeable attribute."
This casting currently treats "null" as "can not merge", which cascades down to other plugins. Should the returned type be expanded?
The text was updated successfully, but these errors were encountered: