2016-01-21 13:49 GMT+01:00 Skip Lentz <[email protected]>: > 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. >
I was thing of being able to use it as a Metacello-based code delivery conduit, especially since if I combine that with GitFileTree loading from a zip approach, then it could become an all-in-memory approach (no git installation, no external filetree) > Do note that you are rate-limited to 60 requests _per hour_ if you don’t > authenticate. So it’s not much. > I'll keep that in mind if it takes many requests to get the full history. > 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. > Yes, this would be perfect. Thanks! Thierry > > Skip > > On Jan 21, 2016, at 1:37 PM, Thierry Goubier <[email protected]> > 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 <[email protected]>: > >> 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 :) >> > > >
