[ANN] GitHub API Bindings: new version

Hi Mariano,

1) By default it lists the repositories of which you are 1. the owner, 2. a collaborator and 3. an organization member.

So even though you might not contribute to some projects, they are shown in there because you are member of the organization which owns it.

I opened an issue for allowing filters in the bindings when listing repositories: https://github.com/Balletie/GitHub/issues/26.

2) There’s an open issue in the repository for implementing pagination. See here: https://github.com/Balletie/GitHub/issues/1.

Right now, not all repositories are shown because another request should be made to the API for the next “page” of results,

like in the web UI.

The same holds for commits by the way: not all commits in the log of the tool are shown because pagination has to be implemented.

Would be cool to use something like FastTable or FastTree to load new pages on the fly.

Hope I answered your questions :)

Skip

On Jan 21, 2016, at 12:40 PM, Mariano Martinez Peck <[hidden email]> wrote:

Hi Skip,

Very cool! Thanks!

BTW, I am trying the UI tool and I found 2 problems:

1) It lists projects that I have nothing to do with them

2) It does not list some of MY projects

Am I doing something wrong?

On Thu, Jan 21, 2016 at 8:18 AM, Dimitris Chloupis <[hidden email]> wrote:

As usual I can only agree with Sven, this is documentation is for seminars how to write proper documentation. Great work, will give it a try :)

On Thu, Jan 21, 2016 at 1:03 PM Skip Lentz <[hidden email]> wrote:

Thanks for the kind words :).
If you feel like there’s some doc missing I will write something for it, just tell me.

> On Jan 21, 2016, at 11:46 AM, Sven Van Caekenberghe <[hidden email]> wrote:
>
> Wow, great work, beautiful documentation.
>
> An excellent example of the right way to do a Pharo add-on library !
>
> Thank you.
>
>> On 21 Jan 2016, at 11:30, Skip Lentz <[hidden email]> wrote:
>>
>> Hi everyone,
>>
>> I am announcing a new version for the API bindings to GitHub in Pharo.
>> For documentation and information on how to load it, see the new project homepage:
>>
>> https://balletie.github.io/GitHub/ (generated with Pillar. Plug for Damien and Cyril)
>>
>> For a list of changes in this release, follow this link: https://github.com/Balletie/GitHub/releases/tag/v0.5
>>
>> To load absolutely everything, including the tests and the tool, evaluate:
>>
>> Metacello new
>>    baseline: 'GitHub';
>>    repository: 'github://Balletie/GitHub:master';
>>    load: #(tests tool)
>>
>> If you have loaded the tool, it can be opened via the world menu, under “Tools”.
>>
>> Feedback welcome :)
>
>

--

Mariano
http://marianopeck.wordpress.com

Hi Thierry,

Good question, and yes it is possible.

It’s good that you raise this point, I will add a class side instance creation method for this to the GitHub class.

What is nice is that this lowers the barrier for people to try the bindings out.

Do note that you are rate-limited to 60 requests _per hour_ if you don’t authenticate. So it’s not much.

If you use some functionality which requires authentication (for example requesting the logged in user),

you will get a GHBadCredentialsError with a message ‘Requires authentication’. Makes sense to me.

Skip

On Jan 21, 2016, at 1:37 PM, Thierry Goubier <[hidden email]> wrote:

Hi Skip,

this is great; I think you have something important there, and I'm just sad to have far too much to do to contribute... I'd just have a question then: is it possible to use it in anonymous mode? I would like to explore if it could be used as a way to get delivery mode (read-only access) to packages with history/versionning (reusing GitFileTree `build MC metadata from git log` code).

Regards,

Thierry

2016-01-21 11:30 GMT+01:00 Skip Lentz <[hidden email]>:

Hi everyone,

I am announcing a new version for the API bindings to GitHub in Pharo.

For documentation and information on how to load it, see the new project homepage:

https://balletie.github.io/GitHub/ (generated with Pillar. Plug for Damien and Cyril)

For a list of changes in this release, follow this link: https://github.com/Balletie/GitHub/releases/tag/v0.5

To load absolutely everything, including the tests and the tool, evaluate:

Metacello new

    baseline: 'GitHub';

    repository: 'github://Balletie/GitHub:master';

    load: #(tests tool)

If you have loaded the tool, it can be opened via the world menu, under “Tools”.

Feedback welcome :)

Thanks Hernán for your report.

As Sven said, it is not yet present in the stable version of NeoJSON.

But it should not matter as I load the bleeding-edge version.

I will look into this.

Can you tell me which script you used to load the tool? Is it the one in the first e-mail?

On Jan 22, 2016, at 12:02 PM, Hernán Morales Durand <[hidden email]> wrote:

Hi Skip,

Trying your tool in Windows 8.1 and Pharo 5. I wrote my username and password and this is what I get:

MessageNotUnderstood: NeoJSONObjectMapping>>allowNil

(there is no implementor of #allowNil)

Cheers,

Hernán

2016-01-21 7:30 GMT-03:00 Skip Lentz <[hidden email]>:

Hi everyone,

I am announcing a new version for the API bindings to GitHub in Pharo.

For documentation and information on how to load it, see the new project homepage:

https://balletie.github.io/GitHub/ (generated with Pillar. Plug for Damien and Cyril)

For a list of changes in this release, follow this link: https://github.com/Balletie/GitHub/releases/tag/v0.5

To load absolutely everything, including the tests and the tool, evaluate:

Metacello new

    baseline: 'GitHub';

    repository: 'github://Balletie/GitHub:master';

    load: #(tests tool)

If you have loaded the tool, it can be opened via the world menu, under “Tools”.

Feedback welcome :)