Hi Skip,

Trying here, especially interested to see how it handles metadata-less filetree.

- I have no authentification issues (but I had the feeling the GUI wasn't working for a little while)

- I don't get all my repositories (well, in practice allmost none, however I get all the pharo books), so I can't test that metadata-less.

- I get NeoJSON parser errors.

Nice to see that nice graph widget put to good use :) But it could have less white space on the left.

Now, how do I contribute if I want to? Where is the repository I should fork on github? I'm also a taker for a few more comments...

Thierry

2015-11-23 16:25 GMT+01:00 Skip Lentz <skip.lentz@inria.fr>:
Hi everyone,

As part of my internship I am creating bindings to the GitHub API in Pharo.
As a prototype and demo, I have created a small tool last week to do some basic versioning, namely checking out a version, committing a version and showing a log of commits along with a branch tree.

Here���s a screenshot:��http://i.imgur.com/iMfWOvp.png

The repository of the bindings and the tool is here: http://smalltalkhub.com/#!/~Balletie/GitHub
To load the tool into your image, execute:

(ConfigurationOfGitHub project version: #development) load: #tool

Keep in mind that this is tied to GitHub, since internally it uses the API. A nice side effect of this is that everything can be done in-memory. That is, there���s no local copy on the filesystem. One does not even need git installed.

That being said, feel free to take off with my prototype and make it work with e.g. the LibGit bindings in Pharo.

Known bug:
- When selecting a different repository from the dropdown while a version is also selected in the log, one gets a DNU. To work around this for the time being, just deselect the version before you switch repositories.

Let me know what you think and feel free to ask some questions.

Skip