The first bit is taken care of in #161, so please remove that. Please also add documentation and unit tests, rebasing once done. Thanks!

As far as I can tell, #161 is for contributors (people who have written
code merged in the project), but my commit adds support for collaborators
(people with commit/admin rights on the project), which is different.

On Wed, 29 Apr 2015 17:15 Ændrew Rininsland [email protected]
wrote:

The first bit is taken care of in #161
#161, so please remove that.
Please also add documentation and unit tests. Thanks!

—
Reply to this email directly or view it on GitHub
#180 (comment).

As far as testing, there are no tests for issues yet, and listCollaborators requires a user with priviledges on the repository, which is not the case of the test user (thankfully), so it'll always return a 403.

Closed in error; reopening.

Hi @raphink. Are you still interested in updating this PR?

@AurelioDeRosa sure. What changes are still required?

This PR needs tests and also to add documentation to the README file. Thank you for the interest.

@AurelioDeRosa Any comment on #180 (comment) ? Has the situation changed regarding testing since?

We have tests for issues now. You can find them in the test folder.

OK I'll have a look.

@AurelioDeRosa I have rebased and added tests

@AurelioDeRosa @clayreimann any news from this?

It's not merged yet (obviously) and two of the three APIs you're adding have been added already, but I'll get issue events in today or tomorrow.

Is collaborators added?

I believe so. We have both contributors and collaborators

@raphink you can see the docs for contributors and collaborators

Thanks. I'll have to rebase my code.

@raphink This is released with version 2.2.0

Thank you.