Tools moving to Git

As part of the spring cleaning this year I want to get all my toolserver tools in source control. Right now most tools are either in SVN, or not in source control at all. The ones in SVN have a directory in my Toolserver SVN repository in under trunk/[name-of-tool].

Each of those will be getting a Git repository. I will be (one-way) mirroring all of those repositories on my GitHub account.

For issue tracking I never had a central location, but I’m really liking the Issue tracker that GitHub provides for repositories. So I’ll start referring to that as the central issue tracker for tools.

As a start I’ve moved these into Git, and mirrored on GitHub:

The base class now has a new feature that can add a “Source code” and “Issue tracker” link in the header. For SVN or Git hosted tools the “Source code” link will point to an online viewer of that repository. And for tools mirrored on GitHub, the “Issue tracker” link will point to the Issue tracker of the GitHub project.

Last but not least, the header now shows the revision hash of the deployed version of the tool. Check OrphanTalk2 for example.