gitoxide icon indicating copy to clipboard operation
gitoxide copied to clipboard

An idiomatic, lean, fast & safe pure Rust implementation of Git

Results 148 gitoxide issues
Sort by recently updated
recently updated
newest added

This is the continuation of [the base PR](https://github.com/Byron/gitoxide/pull/473) to clean up some loose ends. ### Tasks * [ ] extended flags protection (or write them properly) * [ ] long...

We want shallow clones and this issue tracks what needs to be done to get there. ## Prerequisite tasks for bare clones * [x] #474 * [x] #473 * [x]...

C-tracking-issue

Only interpret and make accessible all values and figure out how to bridge different formats in a single implementation ideally. ### Reading * [x] V3 reading + V4 reading with...

C-tracking-issue

First steps towards interacting with and using remotes. ### Tasks * [x] list existing remotes names * [x] find remote by name * [x] deduplicate ref-specs (by instruction), in a...

This issue collects thoughts and facts about the state of shallow clones for git repositories when used by cargo. Here is a list of steps to take in `cargo` to...

C-integrate-gitoxide

A way to obtain a set of attributes given a path, efficiently. Each path we handle needs one lookup there during checkout, thus it must be lazy and per thread....

A probably incomplete collection of features we still want to see in `git-repository` before it can possibly see a first stable release. ### initialization * [ ] make it easy...

C-tracking-issue

This is a fun research project to potentially drive feature development one day to allow replacing git2 with gitoxide. In order to migrate, not all features would have to be...

C-integrate-gitoxide

Clone an entire repository via `gix repository clone` and checkout a working tree along with a valid index. ### Tasks * **git-odb** * [x] all docs, sans examples * [x]...

C-tracking-issue

Note that we handle both crates here as they are very much intertwined. `git-index` handles the data structure to accelerate operations in the `git-worktree` for actually manipulating the working copy....

C-tracking-issue