Skip to content
GEDCOM plugin for Git
Ruby Java
Find file
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.


  • Status: experimental
  • Author: John Sumsion
  • Inspiration: Git, Tim Shadel

GEDCOM plugin for Git. As a git subcommand, git-ged lets you import and manage GEDCOM files in a versioned, shareable way in a Git repository.

It is also possible to attach to other repositories and fetch related genealogy data from others who have imported it into their own repository.

As a library, git-ged lets you write programs that communicate genealogical data in the git-ged repository layout.

As a repository implementation, git-ged also defines a repository specification that, if adhered to by alternate implementations will render all implementations to share repositories with each other.

The genealogical data format for persons and relationships is yet to be decided. The first cut will be one that is largely one-to-one compatible with GEDCOM 5.5. I fully expect to change the format before this solidifies, and I'll use whatever is the commonly-accepted format.

NOTE: Although I started git-ged and have worked on it while being employed by FamilySearch, this project is not endorsed and is not supported in any way by FamilySearch. I work on it outside of work hours, and do not use internal FamilySearch servers or data privileges. It is a personal endeavor to enrich the genealogy data sharing ecosystem.



Easiest install is via RubyGems:

$ gem install git-ged


Git-ged's Git repo is available on GitHub, which can be browsed at:

and cloned with:

git clone


You will need these gems to get tests to pass:

  • mocha


If you'd like to hack on git-ged, follow these instructions. To get all of the dependencies, install the gem first.

  1. Fork the project to your own account
  2. Clone down your fork
  3. Create a thoughtfully named topic branch to contain your change
  4. Hack away
  5. Add tests and make sure everything still passes by running rake
  6. If you are adding new functionality, document it in
  7. Do not change the version number, I will do that on my end
  8. If necessary, rebase your commits into logical chunks, without errors
  9. Push the branch up to GitHub
  10. Send a pull request for your branch




Copyright (c) 2011 John Sumsion. See LICENSE for details.

Portions Copyright (c) 2010 Tom Preston-Warner. See LICENSE.grit for details. Thanks to the github folks for the inspiring Grit gem.

Something went wrong with that request. Please try again.