Chris Rebert

Problem: Seems to be missing an API for https://developer.github.com/v3/repos/#list-branches Filed https://github.com/jcabi/jcabi-github/issues/1084 Submitted PR: https://github.com/jcabi/jcabi-github/issues/1085 - [x] Merged?

Problem: Seems to be missing API for https://developer.github.com/v3/orgs/members/#check-public-membership , equivalent to `OrganizationService.isPublicMember`: https://github.com/jcabi/jcabi-github/issues/1091 Submitted PR: https://github.com/jcabi/jcabi-github/pull/1107 - [x] Merged?

X-Ref: https://github.com/twbs/rorschach/issues/26

Annoyance: https://github.com/jcabi/jcabi-github/issues/1109 - [x] Submitted PR?: https://github.com/jcabi/jcabi-github/pull/1118 - [x] Merged?

Now we're just blocked on the release of jcabi-github v0.24.

That release has occurred, so we should now be unblocked.

Your analysis is correct. I haven't had much time for Savage lately, and so the Authorization header logic is outdated relative to Travis's awesome bugfix.

Yeah, PRs welcomed. I'm happy to translate to Scala from Java if necessary.

Assuming we pull in BouncyCastle for the public-key crypto, the verification part should start with doing `Signature.getInstance("SHA1WithRSA", "BC")` (based on Travis's code samples, they're using SHA-1 + RSA) and then...

Okay, think I've got the crypto part all figured out now. PR incoming.