Open a git repository

Create a "fake" repository to wrap an object database

Look for a git repository and copy its path in the given buffer The lookup start from base_path and walk across parent directories if nothing has been found. The lookup ends when the first repository is found, or when reaching a directory referenced in ceiling_dirs or when the filesystem changes (in case across_fs is true).

Find and open a repository with extended controls

Free a previously allocated repository

Creates a new Git repository in the given folder

Create a new Git repository in the given folder with extended controls

Retrieve and resolve the reference pointed at by HEAD

Check if a repository's HEAD is detached

Check if the current branch is an orphan

Check if a repository is empty

Get the path of this repository

Get the path of the working directory for this repository

Set the path to the working directory for this repository

Check if a repository is bare

Get the configuration file for this repository

Set the configuration file for this repository

Get the Object Database for this repository

Set the Object Database for this repository

Get the Reference Database Backend for this repository

Set the Reference Database Backend for this repository

Get the Index file for this repository

Set the index file for this repository

Retrieve git's prepared message

Remove git's prepared message

Remove all the metadata associated with an ongoing git merge, including MERGE_HEAD, MERGE_MSG, etc

Call callback 'callback' for each entry in the given FETCH_HEAD file

If a merge is in progress, call callback 'cb' for each commit ID in the MERGE_HEAD file

Calculate hash of file using repository filtering rules

Make the repository HEAD point to the specified reference

Make the repository HEAD directly point to the Commit

Detach the HEAD

Determines the status of a git repository - ie, whether an operation (merge, cherry-pick, etc) is in progress