Paŭlo Ebermann

You are right here. The reason for that is that I didn't use JSch for several years, and thus had no need for myself. (Actually I used it just for...

Thanks for the pull request (#8, for the record). I've merged that (via fast-forward) into the tarballs branch, and also merged those commits into master (resolving lots of conflicts). I...

I think the idea for the IdentityRepository is to be a storage of Identity instances (i.e. private keys) – either an internal storage of in-memory keys, or something like an...

I've updated the online version (i.e. the gh-pages branch), after fighting a bit with the fact that javadoc 1.8 seems to avoid overwriting an existing stylesheet.css, and I locally still...

Current documentation state of the new classes: - [x] IdentityRepository (since 0.1.46) - [x] Signature (since 0.1.49) - [x] ConfigRepository (since 0.1.50) - [ ] DHGEX256 (since 0.1.50) - [x]...

@prayerslayer After rebasing (to fix the history) you get new commit IDs. One could possibly get a commit with the same tree ID? Though the commit comments maybe also belong...

Yes, this workaround works. (I don't see a problem with rebasing and force-pushing on a branch which is not yet merged – any problems which can happen here would also...

I think Zappr's approval check could just accept/interpret a native approval as an alternative to a comment with :+1:?

@prayerslayer Not sure how the native approvals look in the API, but if you can get their timestamp (or their relative order in comparison to the pushes), we should still...

Hmm, no timestamp, but a commit id. So we could compare that commit id with the pull request's head sha to see whether the approved commit was the latest one....