gix-index
| Crates.io | gix-index |
| lib.rs | gix-index |
| version | |
| source | src |
| created_at | 2023-02-17 09:48:03.614071 |
| updated_at | 2024-10-22 18:58:53.261869 |
| description | A work-in-progress crate of the gitoxide project dedicated implementing the git index file |
| homepage | |
| repository | https://github.com/GitoxideLabs/gitoxide |
| max_upload_size | |
| id | 787441 |
| Cargo.toml error: | TOML parse error at line 24, column 1 | 24 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
| size | 0 |
Sebastian Thiel (Byron)
documentation
README
Test fixtures
Most of the test indices are snatched directly from the unit test suite of git itself, usually by running something like the following
./t1700-split-index.sh -r 2 --debug
Then one finds all test state and the index in particular in trash directory/t1700-split-index/.git/index and can possibly copy it over and use as fixture.
The preferred way is to find a test of interest, and use its setup code within one of our own fixture scripts that are executed once to generate the file of interest.