Initialize git_rebase_options structure

Initializes a rebase operation to rebase the changes in branch relative to upstream onto another branch process, call git_rebase_next. When you have finished with this object, call git_rebase_free.

Opens an existing rebase that was previously started by either an invocation of git_rebase_init or by another client

Gets the count of rebase operations that are to be applied

Gets the index of the rebase operation that is currently being applied If the first operation has not yet been applied (because you have called init but not yet next) then this returns GIT_REBASE_NO_OPERATION.

Gets the rebase operation specified by the given index

Performs the next rebase operation and returns the information about it If the operation is one that applies a patch (which is any operation except GIT_REBASE_OPERATION_EXEC) then the patch will be applied and the index and working directory will be updated with the changes. If there are conflicts, you will need to address those before committing the changes.

Gets the index produced by the last operation, which is the result of git_rebase_next and which will be committed by the next invocation of git_rebase_commit conflicts in an in-memory rebase before committing them. You must call git_index_free when you are finished with this.

Commits the current patch were introduced during the patch application from the git_rebase_next invocation.

Aborts a rebase that is currently in progress, resetting the repository and working directory to their state before rebase began

Finishes a rebase that is currently in progress once all patches have been applied

Frees the git_rebase object