You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a repo with a required status check. When the PR receives a new commit, that required status check is created and pending -- it might not be set to success or failed until a later time.
But when I list all status checks across all commits, I see all the status checks that are passed/failed, but I don't see the required status check which is still pending. Is that not provided by github via the API, or is there something wrong here?
The text was updated successfully, but these errors were encountered:
Learning more about how this works -- I suspect that github doesn't have a 'required' status as an existing status. The 'required' status list is just a different set of objects per branch defining which are required, and the github UI lists them in the PR next to the actual existing statuses, but that doesn't mean those are returned by the API. I would think they should be, but it looks like that's not the case.
If agreed, I guess we can close this, though I'd love to see this plugin enhanced or another plugin provide that information (required status per branch) so we can make use of it. The lack of that, combined with the 'isMergeable' not taking the required statuses into account, means that there isn't an existing solution to answer the question: "has this PR met it's requirements to be merged'? i.e. is it really mergeable?
I have a repo with a required status check. When the PR receives a new commit, that required status check is created and pending -- it might not be set to success or failed until a later time.
But when I list all status checks across all commits, I see all the status checks that are passed/failed, but I don't see the required status check which is still pending. Is that not provided by github via the API, or is there something wrong here?
The text was updated successfully, but these errors were encountered: