FishEye opens your source code repository to help you understand your code and keep tabs on the people who write it. It lets you view user activity, track code changes, and search and navigate through your repository from any Web browser. Nearly everything in your repository has its own URL, down to every single line of code for every revision. Files, branches, repositories, projects, and even people have their own activity stream. FishEye provides easy navigation, powerful search, historical reporting, configurable file annotation and diff views, changeset analysis, RSS feeds, and integration with JIRA, Crucible, Bamboo, Eclipse, and IntelliJ IDEA. FishEye works with Subversion, CVS, Perforce, Git or Mercurial.
0release is a program to generate source and binary releases automatically. With minimal configuration, 0release will generate a source tarball release candidate, build it to create a binary archive, upload them to your Web server, check the uploads, and tag the release in GIT and update the version number. It can run unit-tests and custom actions, such as building documentation, etc. For Zero Install users, it can also upload a signed XML metadata file about the release, allowing these users to upgrade automatically. Releases are signed with your GPG key.
Git# is a C# implementation of the Git version control system for the .NET platform. It is meant to be fully compatible to the original Git implementation in C for Linux. It can be used as a stand-alone command line application (potentially replacing msysGit on Windows) or as a library for applications such as GUI frontends or plugins for IDEs.
CVS, GIT, and Mercurial as well as other well-known version control systems cannot version directories. In other words, you cannot add empty directories. A "workaround" for this issue is to use placeholder files that are placed into empty directories. These placeholder files can then be committed into the repository and will make sure that, upon checkout, the directory tree is entirely reconstructed. The problem with using placeholder files is that you need to create them, and need to delete them if they are not necessary anymore (because sub-directories or real files were added). With big source trees, managing these placeholder files can be cumbersome and error prone. MarkEmptyDirs can manage the creation/deletion of such placeholder files automatically. It creates placeholder files in all empty "leaf" directories. If later on new files or directories are put into such directories, the placeholder files are not necessary anymore, and are removed automatically.
GitBlogger is a small tool that allows you to write blog posts in reStructuredText using an editor of your choice, commit your posts to a git repository, and then have them automatically converted to Blogger blog posts when you push your repository to another repository. GitBlogger handles creating, updating, and deleting Blogger posts in response to changes in the git repository and handles renames in your git repository.
repos-tools is a set of command-line utilities to make work on your code repositories faster and easier. It lets you push, pull, build, and do other things on your repositories all at once. The supported (D)VCSes are Git, Subersion, Bazaar, and Mercurial. For GitHub users, forking, following, watching, and dealing with issues can be done from the shell.