• Git::Repository
  • Git::Repository::Command ⇒ a wrapper for System::Command

Git::Repository depends on Git::Version::Compare, so that comes along for the ride when you install it.

The documentation spells out pretty clearly — " It's a low-level interface that allows calling any Git command, whether porcelain or plumbing, including bidirectional commands such as git commit-tree. ... As a low-level interface, it provides no sugar for particular Git commands."

As such, it's probably a good idea to write your own wrapper for Git::Repository.

Plugins

There are a LOT of plugins for Git::Repository. There are plugins for specific commands:

• Git::Repository::Plugin::Blame
• Git::Repository::Plugin::Diff
• Git::Repository::Plugin::Log
• Git::Repository::Plugin::Status

And there are other ones too:

• Git::Repository::Plugin::AUTOLOAD — lets you call things like $repository->rev_parse() automagically
• Git::Repository::Plugin::Dirty — is_dirty(), has_unstaged_changes(), has_staged_changes(), has_untracked(), diff_unstaged(), diff_staged(), current_branch()
• Git::Repository::Plugin::Info — is_bare(), has_tag(), has_branch(), has_ref()

Reverse dependencies

It also has a lot of reverse dependencies.