chickadee » git

git

Description

A Git interface based on the libgit2 library.

The current version of this extension requires at least libgit2 version 0.23.0, and it has not been tested on versions newer than 0.26.0.

The source for this egg is available here.

Usage

The library is split into two modules, git and libgit2:

 (import (git)) ; or...
 (import (git libgit2))

• The (git libgit2) library is just the libgit2 API, thinly wrapped. Most of the function signatures remain the same, with a few exceptions:
  • Opaque structures are represented as pointer objects (e.g. git_commit).
  • Public structures are represented as locatives (e.g. git_oid).
  • Memory for out parameters and other structures that would typically go on the stack is allocated automatically.
  • Return values are checked where appropriate, signaling an exception of type git when nonzero.
• The (git) library is a higher-level interface, providing Scheme record types for each libgit2 structure and a more Scheme-friendly API.

It's not recommended to mix the two without prefixing one or the other's imports, as the two libraries share many identifiers.

The following documentation applies to the (git) module.

API

Repository

repositoryrecord

repository? objprocedure

A repository corresponds to an on-disk Git repository.

create-repository #!optional path bareprocedure

Creates and returns a new repository at the given path, or the value of current-directory if no path is given. If bare is given and not #f, the repository will be created without a working directory. An error is signaled if the path is invalid or the repository cannot be created.

repository-open #!optional pathprocedure

Opens the Git repository indicated by path, or the value of current-directory if no path is given. path may point to a bare repository, a working directory containing a ".git" directory, or a ".git" directory directly.

repository-path repositoryprocedure

Returns the absolute path to the given repository's Git directory, either the topmost directory in the project (if the repository is bare) or the ".git" subdirectory.

repository-working-directory repositoryprocedure

Returns the absolute path to the given repository's working directory, or #f if the repository is bare.

repository-ref repository refprocedure

Looks up a Git object in the given repository. ref may be a SHA1 string, oid, reference, blob, commit, tag or tree. The returned object will be of type blob, commit, tag or tree, or #f if no object matching the given ref is found.

repository-empty? repositoryprocedure

repository-bare? repositoyprocedure

Returns a boolean indicating whether the given repository is empty (contains no commits) or bare (an exposed git directory without a working directory).

repository-head-orphan? repositoyprocedure

repository-head-detached? repositoyprocedure

repository-head-unborn? repositoyprocedure

Returns a boolean indicating whether the given repository's HEAD (a symbolic reference) is orphaned (unreferenced under the refs namespace), detached (refering to a commit rather than a branch), or has yet to be created, respectively.

OID

oidrecord

oid? objprocedure

An oid is a unique reference to a Git object, corresponding to a 40-character SHA1 object name.

string->oid stringprocedure

Creates an oid from the given string, which should be a 40-character SHA1 hash. An error is signaled if the string is not a valid hash.

oid->string oid #!optional lengthprocedure

Returns the string representation of the given oid. The optional integer length specifies the length of the returned string, up to 40 characters.

oid->path oidprocedure

Returns the string representation of the given oid in the form "xx/...", where "xx" is the first two characters of the SHA1 and "..." is the remainder.

oid=? oid1 oid2procedure

Indicates whether the two oids are the equivalent.

Revspec

parse-revision-specification stringprocedure

Attempts to parse a string as a Git revision specification, returning two values:

• If string specifies a range of revisions, the start and end commit objects.
• If string specifies a single revision, the commit object and #f.
• If string is invalid or fails to match a revision, #f for both values.

For more information about specifying revisions, see http://git-scm.com/docs/git-rev-parse.html#_specifying_revisions.

Reference

referencerecord

reference? objprocedure

A reference is a direct or indirect pointer to a Git commit object. A repository's HEAD is a common example: it is a symbolic reference, referring to the immediate reference "refs/heads/master", which in turn points at a commit.

reference repository refprocedure

Returns the reference specified by the given string ref from the repository. ref must be a string referring to a valid reference, such as HEAD, "ref/heads/master", or "refs/tags/v0.1.0". An error is signalled if the reference doesn't exists.

reference-name referenceprocedure

Returns the name of the given reference.

reference-type referenceprocedure

Returns the type symbol of the given reference, which will be either oid or symbolic.

reference-remote? referenceprocedure

reference-branch? referenceprocedure

reference-tag? referenceprocedure

These procedures return boolean values indicating whether the given reference is a remote, branch, or tag-type reference, respectively.

references-fold kons knil repository #!optional globprocedure

Folds over the given repository's references in unspecified order.

An optional glob pattern string may be used to filter the references returned. If given, it will be matched in "glob" style where a #\? matches any letter, a #\* matches any sequence of letters, and square brackets match a range of characters (such as "[0-9]" for digits). If no glob is given, all references will be provided to kons.

references repository #!optional typeprocedure

Returns a list of all references in the given repository. A type symbol may be given to filter the references, as in references-fold. The order of the resulting list is unspecified.

repository-head repositoryprocedure

Returns a reference to this repository's HEAD (resolved to an OID), of #f if it doesn't exist.

reference-resolve referenceprocedure

Recursively dereferences the given (possibly symbolic) reference, returning a new non-symbolic reference pointing refering directly to an oid.

reference-target referenceprocedure

Returns the oid of the object which the given reference refers. Symbolic references are peeled until a non-symbolic reference is found, as with reference-resolve.

reference-name-set! reference name #!optional forceprocedure

reference-target-set! reference targetprocedure

reference-name-set! changes the name of the given reference to the string name. If force is given and nonfalse, any previously-existing reference of the given name will be overwritten.

reference-target-set! updates a reference to refer to the given target. If reference is an immediate reference (referring to an object ID), target must be an oid, commit, or SHA1 string. If reference is symbolic, target must be a reference or reference name. It is an error to assign a symbolic reference an OID target and vice-versa.

On success, the on-disk repository is updated immediately.

(create-reference repository #!key name target [symbolic] [force]) => referenceprocedure

Creates and returns a new reference in the given repository for the specified name and target. If symbolic is given and not #f, the created reference will be so, and target must be a reference name or reference. Otherwise, target must be a SHA1 string, oid, commit or reference to a commit. If a reference of the given name exists and force is not given or #f, an error is signalled. Otherwise, creation is forced and the old reference will be overwritten.

On success, the on-disk repository is updated immediately.

reference-delete referenceprocedure

Deletes the given reference from its repository.

On success, the on-disk repository is updated immediately.

Branch

create-branch repository name target #!optional forceprocedure

Creates a new branch in the given repository of the given name and target and returns a reference to the new branch. target must be a commit or tag belonging to the repository. If a branch of the given name exists and force is not given or #f, an error is signalled. Otherwise, creation is forced and the old branch is be overwritten.

On success, the on-disk repository is updated immediately.

branch repository name #!optional typeprocedure

Retrieves a reference to the branch of the given name from the repository. name should be a string naming a branch without a leading reference namespace such as "refs/heads/" or "refs/remotes". An error is signaled if no such branch exists.

A type symbol may be given, either local or remote, to specify what type of branch should be looked up; by default, local is used.

branches-fold kons knil repository #!optional typeprocedure

Folds over the given repository's branches.

A type symbol may be given, either local, remote, or all, to specify what type of branches should be listed; by default, all is used.

branches repository #!optional typeprocedure

Returns a list reference objects for each branch in the given repository. A type symbol may be given to filter the branches, as in branches-fold. The order of the resulting list is unspecified.

branch-head? referenceprocedure

Determines whether the given branch reference is its repository's current HEAD.

branch-name referenceprocedure

Returns the name of the given branch reference. This is similar to reference-name, but the leading reference namespace (e.g. "refs/heads") is omitted.

branch-name-set! reference name #!optional forceprocedure

Renames the given branch reference to name, which should be a string. If force is given and not false, any existing branch with the given name will be overwritten.

On success, the on-disk repository is updated immediately.

branch-delete referenceprocedure

Deletes the given branch reference from its repository.

On success, the on-disk repository is updated immediately.

Generic Procedures

These procedures can be used on any objects of the four main Git object types: commit, tree, tag and blob.

object-id objectprocedure

Returns the oid of the given object, which must be a commit, tree, tag or blob.

object-sha object #!optional lengthprocedure

Returns the SHA1 identifier corresponding to the given object, which may be a commit, tree, tag blob, reference, oid or string.

object-type objectprocedure

Returns a symbol specifying the type of the given object, which must be a commit, tree, tag or blob. #f is returned if the object's type cannot be determined.

object=? object1 object2procedure

Indicates whether the two Git objects represent the same thing (judging by their respective oids). Each object should be of type commit, tree, tag or blob.

Blob

blobrecord

blob? objprocedure

A blob corresponds to Git's Blob object type. It represents a chunk of data, generally a file.

Beware name collisions with CHICKEN's built-in blob data type.

blob repository refprocedure

Returns the blob specified by the given ref from the repository. ref may be a SHA1 string, oid, or blob. An error is signaled if no such blob exists.

blob-id commitprocedure

Returns the oid of the given blob.

blob-content blobprocedure

Returns a blob (of the CHICKEN built-in type) of the contents of the given blob (of the Git object type).

blob-length blobprocedure

Returns the size in bytes of the given blob.

blob-binary? blobprocedure

Indicates whether the given blob is (likely to be) a binary chunk or not.

create-blob repository sourceprocedure

Creates a new blob in the given repository.

source is the data source for the blob, and may be a blob (of the CHICKEN built-in type) or a pathname string indicating a file on the local disk or, if such a file isn't present, a file relative to the repository's working directory.

On success, the on-disk repository is updated immediately.

Commit

commitrecord

commit? objprocedure

A commit corresponds to Git's commit object type.

commit repository refprocedure

Returns the commit specified by the given ref from the repository. ref may be a SHA1 string, oid, reference or commit. An error is signaled if no such commit exists.

(commits-fold kons knil repository #!key [initial] [hide] [sort]) => objectprocedure

Folds over the given repository's commits. If an initial commit or SHA1 is given, only commits that are ancestors of that revision will be returned. If a list of revisions to hide is given, they and their ancestors will be ignored. If a sort order is specified, commits will be collected in the given order; this sort order must be one of the symbols none, topo, time or reverse, or a list of such symbols.

commits repository #!rest argsprocedure

Returns a list of the commits in the given repository. args follows the #!key arguments specification for commits-fold. The order of the resulting list is opposite that of a call to commits-fold with the same arguments.

commit-id commitprocedure

Returns the oid for the given commit.

commit-time commitprocedure

commit-time-offset commitprocedure

commit-time and commit-time-offset return the timestamp of the given commit and its UTC offset in minutes, respectively.

commit-message commitprocedure

commit-message-encoding commitprocedure

Returns the full commit message or message encoding for the given commit.

commit-header commitprocedure

Returns a string header for the given commit, which is a textual display of its author, committer, tree and parent commit.

commit-tree commitprocedure

commit-tree-id commitprocedure

Return the tree associated with the given commit and its oid, respectively.

commit-author commitprocedure

commit-committer commitprocedure

commit-author and commit-committer return the given commit's respective signatures.

commit-parentcount commitprocedure

commit-parent commit #!optional nprocedure

commit-parent-id commit #!optional nprocedure

commit-parents commitprocedure

commit-ancestor commit #!optional nprocedure

commit-parentcount returns the number of parents of the given commit.

commit-parent returns the nth parent of the given commit, or the first parent if no n is given. If the commit has no parent, #f is returned.

commit-parent-id is as commit-parent, but it returns the oid of the given commit's parent without first reading the parent commit from the repository.

commit-parents returns the possibly-empty list of all parents of the given commit. The order of this list is unspecified.

commit-ancestor returns the nth ancestor of the given commit, or #f is no such ancestor exists. n defaults to 1, meaning the commit's first parent (making (commit-ancestor c 1) equivalent to (commit-parent c)).

(create-commit repository #!key message author [committer] [tree] [parents] [reference]) => commitprocedure

Creates and returns a new commit in the given repository. The string message will be used as the commit's message and tree will be the file tree of the commit. If no tree is given, the current state of the repository's index is used. parents may be be a (possibly empty) list of commits to be used as this commit's ancestors. author and committer should be signatures; if committer is not given, author will be used for both. reference, if given and not #f, should be the reference or name of a reference that will be updated to point to the newly-created commit.

Note that if no reference is given, the commit will be created in Git's database but will not be reflected in any of the repository's branches. To update the the working branch with the new commit, for example, use "HEAD".

On success, the on-disk repository is updated immediately.

merge-base repository commit1 commit2procedure

Returns the nearest common ancestor for the given commits. commit1 and commit2 may be commits, commit oids, or SHA1 hashes.

Tag

tagrecord

tag? objprocedure

A tag corresponds to Git's Tag object type, which is a way to mark a specific object as special in some way.

tag repository refprocedure

Creates and returns the tag specified by the given ref from the repository. ref may be a SHA1 string, oid, or tag. An error is signaled if no such tag exists.

tags-fold kons knil repositoryprocedure

Folds over the given repository's tags in unspecified order.

tags repositoryprocedure

Returns a list of all tags in the given repository. The order of the resulting list is unspecified.

tag-id tagprocedure

Returns the oid for the given tag.

tag-type tagprocedure

Returns the object type symbol of the target of the given tag, which will be one of commit, tree, blob, or tag.

tag-name tagprocedure

tag-message tagprocedure

Return the name or message of the given tag.

tag-tagger tagprocedure

Returns the signature of the tag's creator.

tag-peel tagprocedure

Recursively dereferences the given tag until a non-tag object to which it refers is found (and returned).

tag-target tagprocedure

tag-peel tagprocedure

tag-target returns the object referred to by tag, which will be of type commit, tree, blob or tag.

Returns the object immediately referred to by tag, which will be of type commit, tree, blob or tag.

tag-delete tagprocedure

Destroys the given tag.

On success, the on-disk repository is updated immediately.

(create-tag repository #!key target name message tagger [force]) => tagprocedure

Creates and returns a new tag in the given repository for the specified name, message and target. name and message must be strings, tagger must be a signature,and target must be a commit, tree or blob. If a tag of the given name exists and force is not given or #f, an error is signalled. Otherwise, creation is forced and the old tag will be overwritten.

On success, the on-disk repository is updated immediately.

Tree

treerecord

tree? objprocedure

A tree corresponds to Git's Tree object type, which represents a directory tree.

tree repository refprocedure

Returns the tree specified by the given ref from the repository. ref may be a SHA1 string, oid, or tree. An error is signaled if no such tree exists.

tree-id treeprocedure

Returns the oid for the given tree.

tree-entrycount treeprocedure

Returns the number of entries in the given tree. This count does not include entries of contained directories.

tree-ref tree keyprocedure

Returns a tree-entry object for the given key from the tree, or #f if no such tree entry is found. key may be a zero-based integer index or a pathname string relative to the repository's working directory.

tree-fold kons knil treeprocedure

Folds over each path and accompanying tree-entry in the given tree in unspecified order.

Note that kons should be a function of three arguments; the path to the current tree-entry (a string, relative to the repository's working directory), the current tree-entry, and the current state of the fold.

tree-entries treeprocedure

Returns an alist of all tree-entry objects in the given tree, whose keys are pathname strings indicating each tree-entry's location in the tree and whose values are the tree-entry objects themselves. The order of the resulting list is unspecified.

create-tree repository #!optional indexprocedure

Creates and returns a new tree object from the state of the given index in the given repository.

If index is not given, a fresh index for the repository is used. This means the resulting tree will be identical to that of the repository's HEAD.

On success, the new value is written immediately to disk.

Tree Entry

tree-entryrecord

tree-entry? objprocedure

A tree-entry represents a single node in a tree object.

tree-entry-id tree-entryprocedure

Returns the oid of the given tree-entry.

tree-entry-name tree-entryprocedure

Returns the name of the given tree-entry.

tree-entry-attributes tree-entryprocedure

Returns the Unix file attributes of the given tree-entry.

tree-entry-type tree-entryprocedure

Returns the object type symbol, either tree or blob, of the given tree-entry.

(tree-entry->object [repository] tree-entry) => objectprocedure

Returns an object of type tree or blob from the given tree-entry and repository, which must be the owner of the tree-entry.

If no repository is given, tree-entry->object will attempt to determine the owning repository from the tree-entry. This is only possible if the tree-entry belongs to a tree; if it belongs to a tree-builder, instead, an error will be signaled.

Tree Builder

tree-builderrecord

tree-builder? objprocedure

A tree builder provides a way to construct tree objects in memory and write them to a repository, without using an index as an intermediary.

make-tree-builder objectprocedure

Creates a new tree-builder. If object is a tree, it is used as the constructed tree's initial state. Otherwise, object must be a repository, and the resulting tree-builder is initialized with an empty tree.

tree-builder-insert tree-builder object name attributesprocedure

Inserts object into the tree-builder's tree under the given filename name. The inserted object must be a tree or blob, and will have the given attributes (an integer file mode).

tree-builder-ref tree-builder pathprocedure

Returns the tree-entry from the given tree-builder at path, which should be a filename string. If the requested file doesn't exist, #f is returned.

tree-builder-remove tree-builder pathprocedure

Removes the object at the given path from the tree-builder's tree.

tree-builder-write tree-builderprocedure

Writes the tree-builder's current state, modifying the on-disk repository on success. The resulting tree is returned.

tree-builder-clear tree-builderprocedure

Removes all objects from the given tree-builder.

Diff

diffrecord

diff? objprocedure

A diff is the cumulative difference between two Git trees (or tree-like objects). It consists of a number of diff-deltas, each of which represents the difference in a single file.

diff repository #!optional object1 object2procedure

Returns a diff between two objects in the repository.

diff's behavior is as follows, given the following arguments:

• (): diff the repository's index to its working directory
• (index): diff the given index to the repository's working directory
• (tree): diff the given tree to the repository's working directory
• (tree tree): diff the given trees
• (tree index): diff the given tree to the given index

diff-fold kons knil diffprocedure

Folds over the given diff's diff-deltas in unspecified order.

(diff-deltas {{diff}}) => (list-of diff-delta)procedure

Returns the list of diff-deltas for all changed files in the given diff.

diff-deltarecord

diff-delta-path diff-deltaprocedure

diff-delta-old-file diff-deltaprocedure

diff-delta-new-file diff-deltaprocedure

diff-filerecord

diff-file? objprocedure

diff-file-id diff-fileprocedure

diff-file-path diff-fileprocedure

diff-file-size diff-fileprocedure

diff-file-mode diff-fileprocedure

A diff-delta is the difference in a single file between two Git trees. Each delta has a path, a status, a pair of diff-files for the old and new files (retrieved by diff-delta-old-file and diff-delta-new-file, respectively), and a list of diff-hunks representing individual changes.

Each diff-file has an id, path, size and mode (Unix file attributes).

diff-delta-status diff-deltaprocedure

Returns a symbol representing the status of a diff-delta, which will be one of the following symbols, or a list of them if the diff-delta's file is in multiple statuses:

   unmodified
   added
   deleted
   modified
   renamed
   copied
   ignored
   untracked

diff-patch diff nprocedure

Returns a patch for the nth diff-delta in the given diff.

diff-patches diffprocedure

Returns a list of patches for all diff-deltas in the given diff.

diff->string diffprocedure

Returns a string representation of the given diff as a patch.

This is equivalent to concatenating the string representations of each patch given by diff-patches.

diff-old-file diffprocedure

diff-new-file diffprocedure

Returns the diff-file object for the old and new file of the given diff, respectively. If the file is added or deleted, #f will be returned for the diff's old or new file, respectively.

diff-delta-hunks diff-deltaprocedure

Returns the list of diff-hunks in the given diff-delta.

diff-hunkrecord

diff-hunk? objprocedure

diff-hunk-header diffprocedure

diff-hunk-old-lines diffprocedure

diff-hunk-old-start diffprocedure

diff-hunk-new-lines diffprocedure

diff-hunk-new-start diffprocedure

A diff-hunk represents a group of changes in a diff, with some surrounding context. Each has a header describing the change, line counts and start offsets for the old and new versions of the hunk, and a list of diff-lines representing each added or deleted range of bytes in the group of changes.

diff-hunk-lines diffprocedure

diff-linerecord

diff-line? objprocedure

diff-line-origin diffprocedure

diff-line-content diffprocedure

diff-line-num-lines diffprocedure

diff-line-old-lineno diffprocedure

diff-line-new-lineno diffprocedure

A diff-line is a range of bytes in a diff-hunk and represents either an addition, a deletion, or a range that is present in both the old and new versions of the hunk but is included for context. Which of these a given diff-line corresponds to is indicated by its diff-line-origin, one of #\+, #\- or #\space.

Patch

patchrecord

patch? objprocedure

A patch is a textual representation of a diff-delta.

patch->string patchprocedure

Returns the string representation of the given patch.

patch-size patchprocedure

Returns the total number of bytes in the patch, including hunk and line headers and context lines.

patch-stats patchprocedure

Returns a three-element vector containing the number of lines of context, number of lines added, and number of lines deleted in the patch.

Status

file-status repository pathprocedure

Returns the status of the file specified by path in the given repository.

This status will be one of the following symbols, or a list of them if the file is in multiple statuses:

   current
   index/new
   index/modified
   index/deleted
   worktree/new
   worktree/modified
   worktree/deleted
   ignored

file-statuses-fold kons knil repositoryprocedure

Folds over each path and the corresponding file's status in the given repository's working directory in unspecified order.

Note that kons should be a function of three arguments; the pathname of the current file (a string, relative to the repository's working directory), the current status symbol, and the current state of the fold.

file-statuses repositoryprocedure

Returns an alist of all file statuses in the given repository, whose keys are pathnames to each file and whose values are the status symbols of those files. The order of the resulting list is unspecified.

file-ignored? repository pathprocedure

Returns a boolean indicating whether the given path in repository is ignored by Git or not.

Ignore

path-ignored? repository pathprocedure

Returns a boolean indicating whether the given path in repository is ignored by Git or not. This is equivalent to file-ignored?.

ignore-add! repository globprocedure

Adds glob as an ignore rule to the given repository. Files matching this pattern will be ignored for all operations on the in-memory repository. Rules added in this way are not be persisted to the file system.

ignore-clear! repositoryprocedure

Removes all ignore rules that have been added to the repository by ignore-add!.

Note

noterecord

note? objprocedure

A note is a type of reference, stored under the refs/notes namespace. It's used to associate some data (accessible via note-message) with an object.

note-message noteprocedure

note-id noteprocedure

note-message and note-id return the string content and oid of the given note, respectively.

note repository object #!optional referenceprocedure

Returns the note associated with the given object in the repository. reference may be a string specifying an alternative notes reference namespace, which defaults to "refs/notes/commits". An error is signaled if no such note exists.

(delete-note repository #!key target author [committer] [reference]) => voidprocedure

Deletes all notes for the given object target by the given author in the repository. author and committer should be a signatures, while reference may specify an alternative notes reference namespace, which defaults to "refs/notes/commits".

On success, the note is removed from disk immediately. An error is signaled if no such note exists.

(create-note repository #!key message target reference author [committer] [force]) => noteprocedure

Creates and returns a new note in the given repository with the specified message and target object. author and committer should be signatures, while reference may specify an alternative notes reference namespace, which defaults to "refs/notes/commits". If force is given and not #f, an existing note for the same target and author/committer will be overwritten; otherwise, an error will be signaled if such a note already exists.

On success, the on-disk repository is updated immediately.

notes-fold kons knil repository #!optional referenceprocedure

Folds over the given repository's notes in unspecified order.

reference may specify an alternative notes reference namespace, which defaults to "refs/notes/commits".

notes repository #!optional referenceprocedure

Returns a list of all notes in the given repository. The order of the resulting list is unspecified.

reference may specify an alternative notes reference namespace, which defaults to "refs/notes/commits".

Index

indexrecord

index? objprocedure

An index represents the on-disk state of Git's working tree. Changes made to a given index exist only in memory until written to disk using index-write.

index-open repository-or-pathprocedure

It repository-or-path is a repository, index-open returns the repository's index. If it's a string, index-open creates and returns the index at the given path, signaling an error if such an index doesn't exist. It is not possible to open the index of a bare repository, and doing so will result in an exception.

index-entrycount indexprocedure

Returns the total number of index entries entries of the given index, respectively. This is essentially a count of all files tracked by Git in a given repository.

index-read indexprocedure

Updates the given index to reflect the current state of the on-disk repository.

index-write indexprocedure

Writes the state of the given index from memory onto disk, modifying the repository on success.

index-clear indexprocedure

Removes all enries from a given index.

index-add index path #!optional stageprocedure

Adds a given path, which must refer to a file relative to the index's repository, to the index. If an integer stage is given, it will be used as the staging number for the changes.

index-remove index refprocedure

Removes an entry from the given index. ref may be a file path string or an zero-based integer index. If no entry is removed, #f is returned.

index-find index pathprocedure

Returns the zero-based integer index of the file specified by path in the given index, signaling an error if it doesn't exist.

index-ref index key #!optional typeprocedure

Returns the index-entry from the index for the given key, which may be an zero-based integer index or a pathname string, or #f if no such entry exists. If a type symbol is given, either merged (the default behavior) or unmerged, the search will be limited to such entries.

Index Entry

index-entryrecord

index-entry? objprocedure

An index-entry represents a tracked file in Git's working directory, belonging to an index.

index-entry-id index-entryprocedure

Returns the oid referring to the given index-entry.

index-entry-path index-entryprocedure

Returns the file path of the given index-entry relative to the owning repository's working directory.

index-entry-ctime index-entryprocedure

index-entry-mtime index-entryprocedure

index-entry-dev index-entryprocedure

index-entry-ino index-entryprocedure

index-entry-size index-entryprocedure

index-entry-stage index-entryprocedure

index-entry-uid index-entryprocedure

index-entry-gid index-entryprocedure

index-entry-mode index-entryprocedure

index-entry-flags index-entryprocedure

index-entry-extended index-entryprocedure

These methods return the file attributes for the given index-entry as it exists in its in-memory index.

ODB

odbrecord

odb? objprocedure

An odb offers a direct interface to Git's internal object database.

odb-open repository-or-pathprocedure

It repository-or-path is a repository, returns the repository's object database. If it is a string, creates and returns the object database at the given path, signaling an error if no such database exists.

odb-has-object? odb refprocedure

Determines if the given odb contains the given object ref, which should be a SHA1 string, oid or Git object of type commit, blob, tree or tag.

odb-read odb refprocedure

Reads the given object ref from the database, signaling an error if it doesn't exist. ref should be a SHA1 string, oid or Git object of type commit, blob, tree or tag.

odb-write odb data #!optional typeprocedure

Writes a given data blob to the odb, returning an oid referring to the newly-created object. The type of the stored data can be specified by an optional type symbol, which defaults to blob.

odb-hash odb data #!optional typeprocedure

Returns an oid reference for the given data blob as though it had been stored to the given odb but without writing it to disk. The type of the hashed data can be specified by an optional type symbol, which defaults to blob.

ODB Object

odb-objectrecord

odb-object? objprocedure

An odb-object is a reference to a blob of data in a Git object database.

odb-object-id odb-objectprocedure

Returns the oid for the given odb-object.

odb-object-size odb-objectprocedure

Returns the size of the odb-object's data in bytes.

odb-object-type odb-objectprocedure

Returns the object type symbol of the given odb-object.

odb-object-data odb-objectprocedure

Returns a blob consisting of the odb-object's data.

Signature

signaturerecord

signature? objprocedure

A signature is a record of the name, email, time and UTC offset of a given Git object.

make-signature name email #!optional time offsetprocedure

Returns a new signature for the given name and email strings. If a timestamp time and integer offset are given, they will be used as the signature time; otherwise, the current time will be used.

Unlike the create-* functions, no representation of this signature is created in the repository; it exists only in memory until associated with a commit or tag.

signature-name signatureprocedure

signature-email signatureprocedure

signature-name and signature-email return strings for the given signature's respective fields.

signature-time signatureprocedure

signature-time-offset signatureprocedure

signature-time and signature-time-offset return the timestamp of the given signature and its UTC offset in minutes, respectively.

Checkout

checkout repository #!optional objectprocedure

checkout updates files in the working directory and index of the given repository to match the state of object.

If object is an index, the repository's working directory will be updated to match the its state.

If object is a commit, tag or tree, the repository's working directory and index will both be updated to reflect its state.

If object is omitted or #f, the repository's working directory and index will both be updated to match the state of the repository's HEAD.

Note that checkout will silently delete untracked files and overwrite changes to tracked files in the repository's working directory.

Clone

clone url pathprocedure

Clones the remote Git repository specified by url into the local pathname path.

On success, the branch indicated by the HEAD reference of the remote repository is checked out as a normal (i.e. non-bare) Git working directory.

An error is signaled if the clone fails for any reason.

Remote

remoterecord

remote? objprocedure

A remote represents a remote repository.

remote-name remoteprocedure

remote-name-set! remote nameprocedure

remote-name returns the name of the given remote, for example "origin".

remote-name-set! changes the name of the given remote to the string name.

On success, the on-disk repository is updated immediately.

remote repository nameprocedure

Retrieves the remote of the given name from the repository. An error is signaled if no such remote exists.

remotes repositoryprocedure

Returns a list of all remotes in the given repository.

Config

configrecord

config? objprocedure

A config represents a Git configuration file, associated with either a repository, the current user, or the system-wide Git installation.

config-path #!optional typeprocedure

Returns the path to a Git configuration file, if one exists. type may be a symbol specifying the type of path to search, either user, system or xdg, to request the path to the configuration for the current user, the system-wide Git installation, or the configuration file path specified by the XDG standard (".config/git/config"), respectively. type defaults to user. An error is signalled if no configuration file is found at the requested location.

config-open #!optional sourceprocedure

Reads the Git configuration file indicated by source, which may be a repository, path, or symbol as expected by config-path. An error is signalled if no configuration file is found at the requested location.

config-get config name #!optional typeprocedure

Returns the value of the property name in the given config object. The value is returned as a string, unless an alternative return type is specified by the given symbol type, which should be string, symbol, number or boolean. An error is signaled if the requested property doesn't exist, or if it cannot be converted to the specified return type.

config-set! config name valueprocedure

Sets the value of the property name in the given config object to the given value.

On success, the new value is written immediately to disk.

config-unset! config nameprocedure

Deletes the property name from the given config object.

On success, the change is written immediately to disk.

History

0.1.0

Initial port to CHICKEN 5.

0.1.1

Fix incorrect handling of create-blob procedure arguments.

0.2.0

Fix memory management issue for public structures in low-level interface.

Author

Evan Hanson

License

Copyright (c) 2013-2021, Evan Hanson, 3-Clause BSD License