crossover between commit1 and commit2

Handle the conflict by accept ours or theirs. The strategy is a list of bool values, where True means accepting ours, and False means accepting th

Return True if the current working directory has conflicts. Otherwise, return False.

Initialize the git repository Parameters ---------- config The configuration object. origin "local" or "remote"

Check if the merge of commit1 and commit2 is novel, that is, A and B are not ancestor of each other.

Lint the code base. The result will be written to the git notes as well as returning it.

List all the files that have conflicts in the current working directory.

List all the files in the specified commit.

List all tags in this repo.

Randomly select a file and a section within the file and let the llm to mutate the code.

Return True if the change from prev_commit to new_commit is good, and False otherwise. If the prev_commit and new_commit are the same commit, retu

merge the commit specified by the commit_id to the current branch.

Merge the notes from the remote repository.

Return migration candidates from human tags. The migrate_count set the upper limit of the number of candidates.

Return migration candidates from other hosts. The migration_count set the upper limit of the number of candidates.

Calculate the pairwise distances between the commits. Return a matrix where the element at (i, j) is the distance between commit i and commit j.

Calculate the pairwise distances from the merge bases to the initial commits.

Get a tree view of the project structure.

Run git prune.

Prune the commits that are reachable.

Push all branches to the remote

Push the notes to the remote repository.

Push the branch to the remote repository along side with the notes.

Randomly sample a file from the project.

Read the commit id of the current HEAD.

Read the note of the specified commit. If commit is None, read the note of the current HEAD. Return None if the note does not exist.

rebase the current branch on the commit specified by the commit_id.

Remove the worktree of the branch.

The branches are used to track the current state of the population

Update the content of the file in the specified commit_id and commit the updated file. new_content can be either a string or bytes, when it is

Update the content of the file in the specified worktree, then commit the updated file.

Mutation of the individual