> On Nov 23, 2015, at 5:31 PM, Peter Uhnak <i.uh...@gmail.com> wrote: > > On Mon, Nov 23, 2015 at 04:25:28PM +0100, Skip Lentz wrote: >> 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 >> <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. > > Do you have any plans to eventually make a "Git Tool" out of it, rather > than GitHub Tool?
Who knows, I like the idea of it. Again, it’s a prototype/demo/experiment of a versioning tool other than Monticello within Pharo. It didn’t take much time to create, so I decided to just try it out. > Why is it tied to GitHub in the first place? Are you planning to support > some github-specific features like issue tracker, etc? Because not being > able to have git repo localy is actually a hindrance and not a "nice > side effect" (unless of course you are using git as monticello). For my project I needed to implement the API bindings to open pull requests. I saw this as another use case of the API and decided to experiment with it, that’s all really.
