I looked all throughout the documentation, and I could not find any method in this library to invoke the GitHub API'scombined status endpoint. It seems that support for it was never added to this library.

The combined status endpoint isnot the same thing aslisting the statuses for a commit (I know this librarydoes support that). Listing all statuses for a commit shows every single status that has ever been set on the commit specified. In contrast, the combined status endpoint returns asingle combined status which indicates only the overall combined status for the commit, taking into account only the most recent status set for each context.

The combined status endpoint allows a single call to the GitHub API to determine whether a specific commit ready to deploy or not, without having to parse through a list of every status on the commit, find the most recent statuses for each context, and then run through the logic manually to determine what the combined state should be based on the specific combination of states from the statuses of each context.

I'm not sure why the combined status endpoint got overlooked when creating this library, as it is not a new addition to the GitHub API (GitHub added it to their APIback in 2014). The combined status endpoint is a very crucial endpoint, as it is the most reliable way to determine if a particular commit has passed all status checks and is ready to be deployed or not.

I used to use theOctokat.js library for anapplication I'm in the process of developing, but I didn't like the way Octokat.js handled pagination so I started to switch to this library instead. However when I realized that the combined status endpoint was not supported by this library I had to stop migrating, as I need support for the combined status endpoint in my application.

Is adding support for thecombined status endpoint to this library something that can be done fairly quickly? I would greatly appreciate it if one this library's developers could give me an estimate of when support for the combined status endpoint could be added and released, as depending on how long it might take I may have to go back to using Octokat.js. Thanks.