NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
crates.io
crates.io, #1295 most downloaded on crates.io
A git-config file parser and editor from the gitoxide project
Latest stable
0.62.2
Last release 29 days ago
24 Oct 2026
Ships on a steady schedule
a new release about every 4 weeks
Nearly every release is documented
notes for 59 of 59 stable releases
1 version withdrawn
withdrawn after publishing
4 years old
60 releases · first in 2023
Drag across the ruler to compare, or tap a release to open it.
add implicit-aware string lookups
add implicit-aware string lookups
Optional configuration settings may need to distinguish an absent key from
a present key without an = separator. Previously, callers had to resolve
sections manually to retain that distinction and apply metadata filters.
Add File::string_implicit() with component and filtered variants, returning
None for absence, Some(None) for an implicit value, and Some(Some(value))
for normalized explicit bytes. The last accepted occurrence wins, including
implicit occurrences. Reuse this resolution for boolean access without
changing existing string() or raw_value() behavior.
Your coding agent can read these notes before it upgrades. Set up the MCP server →
gix-config v0.62.2
Compare
3 commits contributed to the release over the course of 14 calendar days.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
allow configuring the reqwest HTTP client
allow configuring the reqwest HTTP client
Applications need to supply a custom TLS configuration, including an explicit
cryptographic provider, before reqwest builds its HTTP client. The existing
request callback runs too late to configure that client.
Add reqwest::Options::configure_client and build the client lazily when the
first request makes the HTTP options available. Reuse that client for later
requests, retaining the configured options if a failed worker is restarted.
Apply Git's redirect policy after customization so the callback cannot replace
its safeguards for configured request headers or unsafe redirects.
Adding this public option requires existing complete Options literals to
specify configure_client or use ..Default::default().
reqwest HTTP client (7111e30)File::new_section_with_meta() for explicit section origins
Creating a section with its own source, path, include level, or trust previously
required changing the file's metadata first. Add File::new_section_with_meta()
to attach owned or shared metadata directly to one new section, leaving the
file's origin and the defaults for subsequent sections unchanged.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
0115e90)794eeef)1d7bac7)File::new_section_with_meta() for explicit section origins (f83b969)9272d45)80f4b03)d2d078f)95043b9)f819565)1c25831)5fb3dcf)
</details>Headline benefits of this extra-curricular release are various security improvements, and greatly improved error handling and consisstency. Plumbing c
Headline benefits of this extra-curricular release are various security improvements,
and greatly improved error handling and consisstency. Plumbing crates for instance will now
use a standard std::error::Error compatible error type.
Besides that, the tracing of all commands was greatly improved.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
<csr-id-4e0f8ff9b920e75d9554eb58c76e396e50502346/> Keep rust workspace tests inside disposable repositories and isolated environments <!-- agent --> Direct Git launches inherited repository selectors and user configuration even when tests supplied a fixture working directory. Tests of default-environment APIs and local Git transports also shared the runner's environment. A few journey tests wrote beneath source directories or used the source checkout as the repository under test.
Use the shared gix-testtools Git command builder for subprocess setup, isolated
repository options for fixtures, and isolated child processes where the real
environment-reading API must be exercised. Scope CWD changes, copy the fixture
used by an object-write test, and run shell journeys through jtt run. Keep
journey worktrees and example output within their disposable sandboxes and
replace the attributes checkout test with a representative fixture repository.
Prompt examples also run in isolated children and must build successfully; the
old tests could ignore build failures and execute stale cached binaries.
The affected Rust crate suites, internal test-tool build, and max-pure journey
suite pass from a source copy without Git metadata. Signing and Git-daemon
checks use only disposable keys, repositories, and local sockets.
<csr-id-01e9d06173b38b2911c2ca66781bc80da3cc5414/> track semantic emptiness across continuations A bunch of refactoring, and more white-space and continuation related conformance with Git.
<!-- agent --> Quote delimiters do not append bytes to Git's parsed value, so a raw non-empty continuation chunk may still leave the value empty. Track logical bytes and open quote state when deciding whether continuation indentation is significant.
<csr-id-a441bb2419cf959068fd4db227f3a7bd79aadeb2/> don't indent a value that starts on a continuation line
git discards whitespace for as long as the value it has accumulated is
still empty, so the indentation of the line a value starts on is
insignificant — whether that is the line with the = on it, or a later
line reached through a \ continuation. parse::from_bytes::value() only
applied this to the first line: after a continuation it set value_start
to the first byte of the next line, so the indentation became part of the
value.
Given this .git/config:
[alias]
lg = \
log --oneline --graph
git config --get alias.lg reports log --oneline --graph, while
File::raw_value("alias.lg") reported \t\tlog --oneline --graph. The
leading tabs are silently carried into whatever runs the alias, and the
same happens to any continued value written in this shape, such as a
core.pager set over two lines.
value() now emits that indentation as Event::Whitespace for as long as
every chunk seen so far has been empty — the very sequence that
Event::ValueNotDone already documents ("A Newline event usually
follows, followed by either ValueDone, Whitespace, or another
ValueNotDone"). Because the events keep the bytes, to_bstring() still
round-trips the file unchanged, and every consumer already ignores
Whitespace when concatenating value chunks.
Indentation that follows actual content is untouched, matching git:
k = abc\ + \n\tdef stays abc\tdef, and multi-line aliases that begin
on the = line keep their interior whitespace.
<csr-id-7670cefb7809ceaf2bc63b538fb4b9dd569395a2/> migrate errors to gix-error <!-- Byron --> rubberstamp
<csr-id-4b42e0ce80ae934cae4f102f44c392581758608f/> raise MSRV to Rust 1.88
<!-- agent -->
The newly published dua-core 3.3 release used by linked-worktree removal
requires Rust 1.88, so raise every workspace crate and the advertised badge
together.
Keep the MSRV checks buildable by selecting the latest sysinfo and rusqlite
release lines that support Rust 1.88.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
37860b3)6356013)daf73b5)7670cef)65c5dfe)0695cd5)c609062)4e0f8ff)92b6508)2742f05)181297c)36b6310)a095334)4b42e0c)7e35849)888677a)2f154e2)26e8c68)01e9d06)a441bb2)b8914ff)
</details>Headline benefits of this extra-curricular release are various security improvements, and greatly improved error handling and consisstency. Plumbing c
Headline benefits of this extra-curricular release are various security improvements,
and greatly improved error handling and consisstency. Plumbing crates for instance will now
use a standard std::error::Error compatible error type.
Besides that, the tracing of all commands was greatly improved.
remove full-screen progress mode <!-- agent --> Full-screen progress required separate command and UI threads plus channel coordination, while line progress already covers long-running commands and works with independently buffered tracing.
Remove --progress, --progress-keep-open, and the prodash-render-tui feature. Keep synchronous line progress as the only progress UI.
make trace output independently configurable <!-- Byron -->
Quick review only, as it's mostly about tracing and gix which both aren't super
important, and are seemingly working well. An extra agent-review couldn't
find anything either.
<!-- agent -->
Replace the old boolean trace switch with a bounded -t/--trace counter:
forest INFO and DEBUG at one or two occurrences, then flat DEBUG and TRACE at
three or four. Keep --threads long-only and route tracing independently of
verbose and progress rendering, including commands with bespoke execution paths
and corpus runs.
Initialize display tracing once before repository discovery, buffer it outside
prodash, and emit it after command and progress teardown. Format forest and
flat output with ANSI, then adapt the final stderr write so terminals get color
while pipes and NO_COLOR remain plain.
Corpus worker subscribers share that sink while retaining their complete
JSON trace storage, and flat modes include completed spans. gix tix remains
delegated to Tix so it installs only one subscriber.
add and remove linked worktrees from the CLI <!-- Byron -->
rubber-stamp mostly for gitoxide-core changes, did look at it though just to be sure.
Journey test was present but removed.
<!-- agent -->
The CLI previously exposed only worktree listing, despite gix supporting
both checkout and safe removal. Add worktree add (alias create) and
worktree remove using those APIs.
Creation follows Git's local-branch and detached-revision selection, including
destination-basename defaults and -b. It retains new branches after setup
failures, uses the existing listing format on success, and reports incomplete
checkouts. Removal maps repeated -f flags to dirty-worktree and lock overrides
while retaining branches.
Both commands use the existing repository, configuration, and progress options. Unsupported JSON output is rejected before mutation.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
AsHashKind (106db87)gix free index (a8e3143)<csr-id-f3986683be2ab089608dbed3d2248a3dd33207ac/> keep standalone comments separate when replacing continued values <!-- agent --> Replacing a continued value that ended at a comment on the next physical line removed the continuation newline, turning the standalone comment into an inline comment on the replacement value.
Retain the final continuation newline when an empty ValueDone event is followed by a comment. Cover hash and semicolon comments with LF and CRLF, along with quoted comment markers that remain value content. This matches git config parsing behavior.
<csr-id-d1ef42904e94d254d0027fa6da3659dbf6466d21/> decode the config \b escape to the backspace byte, matching git normalize decoded a \b escape in a quoted config value with out.pop(), deleting the preceding byte, so "x\bic{}y" normalized to "y" and a leading \b was silently dropped.
git decodes \b to the backspace character (0x08). Push 0x08 to match, alongside \n and \t.
<csr-id-cf934f16420018899fa2f4d273ab0352d5b6bc92/> an implicit boolean followed by whitespace is true, like in Git.
A key without = is an implicit boolean and reads as true, but only if
nothing at all follows it on the line. A single trailing space or tab turned
it into false:
$ printf '[core]\n\tbare \n' > f $ git config --file f --bool core.bare true # git 2.50.1 (Apple Git-155)
File::boolean("core.bare") -> Ok(Some(false)) File::string("core.bare") -> Some("")
Trailing whitespace after a key is easy to produce by hand or with an editor
that does not strip it, and the mistake reaches porcelain: with
[core]\n\tfileMode \n in .git/config, Repository::filesystem_options()
reports executable_bit: false, so gix stops honouring the executable bit
on a repository where Git still honours it.
key_and_value_range_by_in() decided implicit-vs-explicit by looking at
whether the value event sits directly behind the value name. The parser emits
a Whitespace event between SectionValueName and the synthetic empty
Value when the key has trailing spaces or tabs, which pushed the value one
slot further and made the pair look explicit. Decide on the presence of a
KeyValueSeparator between name and value instead, which is what the
distinction is actually about.
Explicit values are unaffected: bare =, bare = and bare="" still read
as false with an empty string value, matching Git. Lines that Git accepts
only gain the classification Git gives them; lines Git rejects as bad config
(a key followed by a bare word or a comment, with no =) also become
implicit, which is a change but not one Git constrains — see the PR
description.
<csr-id-32df2dba854f1f2c5060a2a8751faef5113d8440/> keep the value when a line continuation is followed by an empty line
A value ending in a continuation backslash was parsed as the empty string
when the continuation line turned out to be empty, discarding everything
accumulated before the backslash. With [core]\n\tk = abc\ as the file
content plus the bytes below, git config --file f core.k prints abc
in every case:
| bytes after the continuation backslash | git | gix-config |
|---|---|---|
\n\n (empty line) |
abc |
`` (empty) |
\n; comment |
abc |
`` (empty) |
\n then EOF |
abc |
`` (empty) |
\n\n[other]\n |
abc |
`` (empty) |
\r\n then EOF |
abc |
`` (empty) |
| EOF, no trailing newline | abc |
abc |
\n \n (blank line with spaces) |
abc |
abc |
value() emits one ValueNotDone per continued chunk and terminates the
sequence with ValueDone, which is what every consumer concatenates. When
the final chunk was empty it took the empty-value shortcut and dispatched a
bare Event::Value instead, and a bare Value reads as a complete value,
so the preceding ValueNotDone chunks were dropped. That also broke the
invariant documented on Event::ValueNotDone, that ValueDone follows it.
The shortcut now dispatches ValueDone when a continuation was seen and
Value otherwise, matching the distinction the non-empty path already
makes. Values without a continuation are unaffected, as are continuation
lines holding only whitespace - those never reached the shortcut, because
the whitespace is trimmed after the branch rather than before it.
Rows 1, 2 and 4 are a regression from 91c854e7b (fix!: remove winnow and replace it with hand-implemented parsers everywhere), which first shipped
in gix-config 0.56.0. Verified by building f26762623, whose gix-config/src
tree (b2fda5bc7) is identical to the one tagged gix-config-v0.55.0, so that
measurement is of released 0.55.0 and 0.55.0 is demonstrably the last
release with the correct behaviour. It is also the last building ancestor:
the immediate parent b060eb24a does not build in isolation, as gix-object
fails against the changed gix-actor API until its "adapt to changes"
follow-up. Rows 3 and 5 were already wrong at f26762623, so those two are
long-standing rather than regressed. Row 6 was a parse error before the
rewrite, fixed by 51279734f.
<csr-id-e7548bad2f7c521c72242c4e54cca6f8c3721671/> normalize expanded git-dir paths on Windows during include matching. <!-- agent --> Git matches includeIf.gitdir conditions against forward-slash paths on Windows. Relative git-dir contexts in gix-config were initially normalized, but their realpath-expanded fallback retained native backslashes and failed to match forward-slash conditions. Normalize that fallback as Git does and make the environment test use the matching form explicitly.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
ebe9095)f3bbfad)gix-testtools (0cbe539)70e98a0)f398668)cc3ee80)ab4fcb0)77dc1ff)1bea62a)484ebac)4a17fdd)d1ef429)true, like in Git. (cf934f1)b95db7c)afe2234)32df2db)50713b0)e7548ba)ae8845a)
</details>Breaking change: gix_worktree::prepare() now accepts the destination first, followed by an add::Context containing the common Git directory and an opt…
preserve sparse-checkout state when adding worktrees
Looked at everything carefully, but was despite test refactoring, I went
through those more quickly. The benchmark I only skimmed.
Adding a linked worktree from a sparse checkout copied its configuration
without its patterns, then materialized the entire target tree. Copy active
info/sparse-checkout patterns from the source worktree's private Git directory
during preparation, including when checkout is deferred. Missing patterns are
skipped, empty files are retained, and copy failures roll back registration.
Expose pattern loading and full-index selection through gix_worktree::sparse.
Initial checkout in gix reads the destination's current patterns and marks
excluded target-tree entries with SKIP_WORKTREE and EXTENDED before writing
files and persisting the index. Support cone and non-cone patterns, case
folding, invalid-cone fallback, root entries, and directory pruning. Sparse
index generation and updates to existing checkouts remain outside this API.
Reuse matching decisions for shared directory ancestors with storage bounded
by path depth, and skip index traversal for a validated full-cone selection.
Cover pattern matching with 18 Git-generated baseline scenarios, regression
tests for cache boundaries and ordering, and integration tests for main and
linked sources, deferred checkout, missing or disabled patterns, and rollback.
Add Criterion benchmarks for cone and non-cone selection on synthetic indices
with 20,000 to 200,000 entries, checking membership and flags before timing.
Breaking change: gix_worktree::add::prepare() now accepts the destination
first, followed by an add::Context containing the common Git directory and
an optional source private Git directory, then its existing options. Use
add::Context::new(common_dir) when pattern inheritance is not wanted.
make bounded removal retries configurable
Went through the tests pretty quickly, as is increasingly common.
Expose Options::retry_delay alongside max_retries. The default is 10 ms;
Duration::ZERO retries immediately, and callers can choose a longer delay for
longer (expected) write bursts. Only retryable DirectoryNotEmpty errors with
attempts remaining wait, before restarting traversal. Successful first-pass
removal, zero-retry operation, and terminal failures incur no pause. The default
two retries request at most 20 ms of sleep per root; filesystem operations and
scheduler delays have no wall-clock bound.
Remove the shrinking-entry-count guard. A writer can replace every deleted file
with a new one, leaving the scan count unchanged even though deletion succeeds
for every scanned entry. The old guard then stops before the configured retry
allowance is used. A deterministic regression writes one replacement after each
of the first two scans: the old loop fails on the second pass; the corrected
loop succeeds on the third, even with a zero delay. The retry count bounds
shrinking, equal, and growing workloads without trying to infer writer progress.
Deletion duration or entry counts cannot tell when an independent writer will
finish. Keep the delay an explicit caller policy instead of introducing another
heuristic tied to tree size. No finite retry policy guarantees completion for
arbitrary finite or indefinite writers. Existing porcelain Target::options()
and the re-exported Options expose this setting without another configuration
layer. Downstream exhaustive Options literals must add retry_delay or use
..Default::default().
cap automatic macOS removal at four workers
This is an APFS problem, which is also noticeable when scanning through
metadata, which now caps at 8 at least in dua.
On Linux Ext4 no such limits exist for all I know, so this commit is
a macOS specific fix to ensure decent performance.
Resolve automatic removal concurrency to at most four available logical CPUs
on macOS. None and Some(0) stay automatic; positive explicit limits remain
unchanged, as do defaults on other platforms. Apply the cap in the shared
plumbing options so repository, proxy, and CLI removal inherit it.
Sixteen concurrent unlink workers contend on native APFS. A dedicated comparison
of three and four workers favors four in all 12 matched pairs, including trees
created by Git, gix, and APFS cloning. Median wall seconds (range), four samples
per cell:
| Creator | 3 workers | 4 workers | Less elapsed time |
|---|---|---|---|
| Git | 2.013 (1.878–2.059) | 1.842 (1.820–1.856) | 8.49% |
| gix | 2.873 (2.849–2.890) | 2.597 (2.577–2.673) | 9.59% |
| APFS CoW | 1.577 (1.571–1.594) | 1.429 (1.420–1.432) | 9.42% |
Median per-round 3/4 time ratios are 1.087×, 1.101×, and 1.107× respectively.
One additional single-worker control per creator took 3.258, 3.911, and 2.781 s:
the four-worker medians are 1.77×, 1.51×, and 1.95× faster. Those controls ran
last and are diagnostic, not paired repetitions.
The preceding native worker sweep measured sixteen-worker medians of 5.018 s
for Git-created and 5.819 s for gix-created trees (two samples each). These are
separate measurements, not additional pairs in this comparison. GitButler's
image-derived one-worker override and the old all-core default both give up
native-volume throughput.
2026-10-09, Apple M4 Max, 16 logical CPUs, 64 GiB RAM, macOS 27.0.1 (26A434),
native APFS under /private/tmp; Rust 1.96.1 release probe and Apple Git 2.54.0.
The cached probe uses local Gitoxide 00bb1af, with max-performance, parallel,
both pack-cache variants, SHA-1, and worktree mutation. Explicit removal thread
limits exercise the same deletion path as the new automatic cap. The retry
pause only applies after an error; no concurrent writes were injected here.
Borrow objects read-only from
/Users/byron/dev/git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux, commit
707df3375124b51048233625a7e1c801e8c8a7fd, using independent seed metadata.
The clean seed checks out tree 176a057fce1932fe5057196e63c2a636e1a3cdab:
88,821 tracked files / 1,509,611,994 blob bytes. Native case-insensitive APFS
requires omitting thirteen later case-fold collisions in git ls-tree -r
order: 15,749 bytes, 0.00104% of the source tree.
Each of four rounds creates fresh Git, gix, and CoW destinations with both
removal counts; odd rounds reverse all case ordering. Git checkout uses one
worker, gix its default sixteen. CoW registers with Git without checkout,
uses clonefile() for regular files and index, and recreates symlinks. This is
a deletion fixture, not a timing of GitButler's entire CoW creation workflow.
A small byte/symlink self-check validates the fixture copier.
Synchronize with sync_volume_np(SYNC_VOLUME_WAIT) before creation and removal,
outside timers. Validate clean status before forced removal, excluding status
cost from the removal timer. All 27 samples removed both checkout and private
administration. No build or other benchmark overlapped measurements. One
0.24 s read-side inventory overlapped the second-round CoW/3 case; excluding
that pair leaves medians 1.577 vs 1.430 s, with four winning all remaining pairs.
These are warm-cache timings on one native APFS machine. No new disk-space,
cold-cache, durable-write, or other-platform measurement was made. The old
sparse-image results are unsuitable for choosing native macOS concurrency.
The updated automatic-resolution test failed with 16 instead of 4 before the
change. Removal and bounded late-write regressions pass, including explicit
limits above the cap. Keep results here; discard temporary fixtures and logs.
classify sparse gitlinks as directories on every host
Non-cone directory-only patterns should treat gitlinks as directories on
every host, including when the destination is initially empty. The original
matcher instead hardcoded them as non-directories, reproducing the result
of Git's little-endian ce_to_dtype() bug.
Expose gix_index::entry::Mode::is_dir_for_git_matching() using decoded
modes directly, and document why Git's extra ntohl() conversion is wrong.
Use this classification for sparse matching, so /*/ includes an absent
gitlink and !/module/ excludes it consistently across hosts.
Keep Git-generated baselines while working around its conversion bug:
pre-create the empty gitlink directory only for the reference operation,
allowing Git's filesystem fallback to recover its intended classification.
The gix index-only regression and initial checkout still start without it.
Check included gitlinks as directories rather than reading them as files.
raise MSRV to Rust 1.88
<!-- agent -->
The newly published dua-core 3.3 release used by linked-worktree removal
requires Rust 1.88, so raise every workspace crate and the advertised badge
together.
Keep the MSRV checks buildable by selecting the latest sysinfo and rusqlite
release lines that support Rust 1.88.
gix editor command
<!-- agent -->
Provide a small plumbing command that opens zero or more paths with
Repository::editor()'s Git-compatible selection. Prepare editor definitions with
command-aware argument splitting so PATH-resolved programs run directly while
actual shell syntax still uses the shell, reject explicitly empty settings, and
honor ':' as the no-op editor.<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix editor command (d930653)
</details><csr-id-d125a59a25540f5945ce235a897b8ef6709624bb/> add parse::format to normalize git-config whitespace.
Adds gix_config::parse::format::normalize(input, &Options), which re-emits a
single config file with sanitized whitespace without resolving includes. Values,
comments and section headers are preserved verbatim; only insignificant
whitespace, the = separator and newlines are rewritten.
Options controls indentation (two spaces by default; tabs or none also
available), spacing around =, the newline sequence (detect/LF/CRLF), the
trailing newline, and optional blank-line collapsing.
This is the library portion; the CLI will follow separately.
<csr-id-ec2895f89f0f76f95ed84d1bc14ccfa927bce504/> return config values with their containing sections via File::*_with_sections() methods.
That way it's easier to know where a value is coming from.
Also streamline arguments and available methods for concistency.
<csr-id-1ce5b56af685e34ccfc564649b51d357b2e24073/> add SectionMut::rename() for precise single-section renames.
This is important now that File::rename_section*() renames all matching
sections.
AsBStrOpt for value pushes.
This makes using the APIs much more convenient.gix-config
Marked as breaking explicitly to as we know paramter types were
changed to use convenience traits.<csr-id-0e3b35bd461ec64867068a548a85d50944abd870/> make parsed configuration files lifetime-free
Store parsed configuration data in a self-contained backing buffer, with
event payloads represented as compact spans into it. This removes the
input lifetime from File and Events, making parsed configurations
easier to return, store, move, and combine.
Expose data through lightweight EventRef, SectionRef, HeaderRef,
and BodyRef views. This retains efficient borrowed access while keeping
ownership details out of the primary API.
Events::from_bytes() and remove
from_bytes_owned().Events::iter(), frontmatter(), and sections() for
non-consuming traversal.BString values from lookups, avoiding Cow handling.Option<Result<T, E>> to
Result<Option<T>, E>.AsBStr and
IntoBStringOpt.new_section("remote", "origin") without
constructing Option<Cow<...>>.Introduce explicit section ownership: Section is self-contained and
can be removed, edited, and inserted into another file, while
SectionRef and SectionMut provide borrowed access.
Preserve original subsection spelling for serialization while retaining decoded names for lookup. Configuration equality now also compares section and value names case-insensitively, matching Git semantics.
Add benchmarks covering section, value, subsection, and multi-value lookups across configurations of varying sizes.
<csr-id-784323a088a7d98d08c17ddfc1e078b98431d2bf/> simplify gix-config section lookup acceleration breaking change for safety, as parameter types were changed.
--- agent
Replace the terminal/non-terminal enum vector with a direct boxed lookup record, use a Vec for section order, and centralize ordered insertion and removal. Empty lookup buckets are removed instead of becoming special cases.
This removes 137 production lines, including 108 lines from the lookup utility, while adding targeted ordering and cleanup coverage.
Back-to-back lookup benchmarks against the previous revision show:
Thus all lookup groups remain within the 5% parity target, with subsection lookup becoming consistently faster.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
Clippy helped 1 time to make code idiomatic.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
parse::format to normalize git-config whitespace. (d125a59)842bc44)cb6ec7d)f0ec710)cfd3899)1825e85)5982dfe)gix-config (6aa934a)File::*_with_sections() methods. (ec2895f)AsBStrOpt for value pushes. (0887485)SectionMut::rename() for precise single-section renames. (1ce5b56)b92d0ff)784323a)c16b5a1)43ff87a)55b5158)0e3b35b)cf3053a)27aec47)e9c973d)d533f0c)1b1541e)
</details>remove gix tix screen selection Remove the plumbing CLI screen-mode option now that the interactive history always owns the alternate screen. The auto
remove gix tix screen selection Remove the plumbing CLI screen-mode option now that the interactive history always owns the alternate screen. The automatic and half-screen modes depended on inline rendering behavior that is being retired from gix-tix.
Stop accepting --screen for gix tix and its aliases, and remove the mode validation and translation into gix-tix. Construct the reduced gix-tix options directly from the remaining quit and hidden-revision arguments. Keep a command-line regression assertion so the removed option cannot silently return as an ignored argument.
delegate tix commands through gix-tix Embed the complete gix-tix Clap platform in the plumbing command instead of maintaining a second parser and dispatcher. This keeps standalone and plumbing invocations aligned, adds worktree-tip parity, and makes amend and spill available through gix tix without duplicating their execution logic.
show other worktree checkouts in tix Decorate commits checked out by other main or linked worktrees with light-blue name@ labels, replacing the ordinary branch label. Keep the checkout from which tix was opened represented by the graph @ marker and its ordinary local reference, and use directory basenames for other detached worktrees. Keep other-worktree labels visible on the selected row when references are hidden.
Add -w/--worktrees to include every successfully resolved worktree HEAD, including the current checkout, alongside implicit or explicit traversal tips without weakening hidden-revision exclusions. Discover worktrees from their private Git metadata so stale checkout directories remain useful, while malformed, unborn, or inaccessible entries are logged and skipped.
Watch linked HEAD and worktree membership changes so decorations and optional tips stay current, while ignoring unrelated linked indexes, logs, and metadata. Document the behavior and cover current, attached, detached, stale, malformed, hidden-reference, CLI, and watcher cases.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
remove linked worktrees safely
Provide the gix-worktree plumbing needed to recursively remove a linked
checkout and its private Git directory without following symbolic links or
crossing Unix mount boundaries.
Use dua-core for traversal and parallel deletion with progress reporting,
bounded retries for directory-not-empty races, and errors distinguishing
checkout and administration failures. Keep repository validation, dirty-state
checks, lock policy, and branch decisions with higher-level callers.
create linked worktrees
Add transactional linked-worktree administration with rollback, then compose
it in gix with existing reference, checkout, index, progress, and interruption
machinery.
Support attached and detached worktrees from bare or non-bare repositories while
rejecting occupied branches and destinations. Keep move, remove, repair, hooks,
sparse checkout, and relative-link configuration out of scope.
skip symlinked ignore files and protect checkout writes
A tracked .gitignore symlink was absent from the skip-worktree ID
mapping, so ordinary ignore lookup could parse arbitrary external files.
An endless target could also exhaust memory.
Always request no-follow reads for worktree .gitignore files, regardless
of their index entry. Use gix_fs::open_read_only_no_follow() when pattern
loading disallows symlinks, treating skipped links as absent files so
skip-worktree blob fallback remains available. Discard partially read
pattern bytes on failure.
Use the same helper for the worktree .mailmap, reporting symlinks as
errors without reading their targets and identifying worktree read errors
correctly. Explicitly configured pattern files and mailmap.file may
still follow symlinks.
On Windows, inspect nonexclusive checkout handles for symlinks before
truncating with set_len(0) or writing. Retain forced unlink-and-replace
behavior and route symlinks checked out as ordinary files through the
same validated open path. No-follow protection applies to the final path
component on Unix and Windows; leading components can still be symlinks.
Compare ignore lookup and skip-worktree fallback against isolated Git
check-ignore calls. Cover mailmap policies and checkout collisions with
file, directory, and dangling symlink targets, including links created
after the Windows path check and validation before truncation.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
6428edc)f7d4f33)
</details>support cloning a single revision <!-- agent --> A full object ID passed through with_ref_name() produced an object-ID refspec mapping and panicked wh
support cloning a single revision <!-- agent --> A full object ID passed through with_ref_name() produced an object-ID refspec mapping and panicked while clone assumed every mapping had a name. Branch and tag checkout also retained ordinary clone tracking semantics instead of offering a single-revision mode.
Add PrepareFetch::with_revision() and gix clone --revision for full refs, HEAD, and full object IDs. Revision clones use a one source-only implicit refspec, detach HEAD to the fetched commit, create no ordinary refs, persist no fetch refspec, and disable tag following. Existing with_ref_name() and --ref behavior stays unchanged.
This follows Git commit 337855629f59 (builtin/clone: teach git-clone(1) the --revision= option) and its t/t5621-clone-revision.sh behavior.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix-date (613ff86)keep descendants of ignored directories excluded
I looked at this carefully, and ended up having a better comment
to provide an example for what this covers.
Ultimately, this is test extension is still minimal compared to the
behaviour that it enables, scoped status, but I think it's fine
in there interest of less code.
Scoped status walks can enter an ignored directory when a pathspec
matches. If a deeper directory matches a negated rule such as !out/,
the ignore stack previously stopped at that nearer match and exposed its
contents as untracked. Tix uses scoped walks for filesystem refreshes,
so ignored Cargo output appeared after unrelated worktree events and
disappeared after a full refresh.
Continue through negated directory matches to check excluded ancestors.
Keep the nearest negation as the fallback when no ancestor excludes the
path, and preserve the precedence of positive directory matches,
including precious-file handling.
Extend the Git-reference fixture below a negated child directory and
refresh both hash archives. The extended fixture fails with the previous
matcher. All directory-walk, status, and worktree tests pass, as do the
SHA-256 ignore baseline, formatting, and Clippy with -D warnings.
Clippy retains the workspace's existing removed-lint warning.
raise MSRV to Rust 1.88
The newly published dua-core 3.3 release used by linked-worktree removal
requires Rust 1.88, so raise every workspace crate and the advertised badge
together.
Keep the MSRV checks buildable by selecting the latest sysinfo and rusqlite
release lines that support Rust 1.88.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
10c58bb)575113d)1bc4ce3)gix-testtools (ce9e6bd)278d7ec)sha1 feature in gix to just set what's needed. (16a6fc4)4743361)1980190)e3d5a04)ab2fee1)2cb17b2)3675a8d)adb8328)
</details>add configurable terminal screen modes.
add configurable terminal screen modes.
hide revision ancestry in tix
add tix to the gix CLI
add explicit gix config show subcommand.
add gix config list for showing the git-configuration files.
add the gix config fmt subcommand
Expose the gix-config whitespace formatter as
gix config fmt [--in-place] [in-file] [out-file]: with no in-file it
formats the repository-local configuration, and with no out-file it writes
to stdout. The repository is only opened when the repository-local
configuration is needed, so formatting an explicit file works outside a
repository too.
add gix status --untracked flag
This allows to control how untracked files are folded, but also
can completely turn dirwalking off.
add gix free remote refs to list and write remote refs.
Add gix free remote refs to perform an upload-pack handshake, discover
the remote reference advertisement, and print the refs without negotiating
or receiving a pack.
The command can also write the advertised refs into a standalone ref store:
gix free remote refs --refs-directory out-refs <url>
preserve multiple remote URLs
Configured remotes can have multiple remote.<name>.url or remote.<name>.pushUrl
values, but gix::Remote kept only one value because lookup used the singular
config accessor. That meant the most recent config value won, while Git exposes
every effective URL and uses the first one for the singular get-url form.
Add ordered URL storage to gix::Remote and expose Remote::urls(Direction) for
all effective URLs. Keep Remote::url(Direction) as the singular compatibility
API, now returning the first effective URL. Fetch URLs used as push fallbacks
try pushInsteadOf first and then insteadOf, matching Git behavior.
The regression fixture records Git 2.50.1 behavior with git remote get-url: without --all it prints the first configured URL, and with --all it prints all configured URLs in order for both fetch and push.
make exclude queries index-aware <!-- agent -->
gix exclude query reported ignore matches for tracked files and directories
containing tracked entries, unlike git check-ignore. Positional arguments were
also interpreted as pathspecs while stdin supplied paths.
Treat positional and stdin input uniformly as paths, normalize them relative to the repository, and suppress ignore matches for indexed files or directories containing indexed entries. This changes positional arguments from pathspecs to paths.
Add journey coverage for tracked and untracked paths below ignored directories, stdin from a nested working directory, ignore-pattern display, and positional output order.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix config list for showing the git-configuration files. (bd595de)gix config fmt subcommand (87a5e89)gix-attributes (e11d7a2)gix-config (376e946)gix status --untracked flag (9316ff8)gix free remote refs to list and write remote refs. (6767b30)
</details>gix-testtools (0cbe539)Store::at() where possible (17fea2a)GIX_TEST_FIXTURE_HASH for more tests (bbea2c4)<csr-id-d4439cd5b5aa82c126198aa57de6a9ebbc15d371/> Limit Commit and Tag parsing to a given gix_hash::Kind
Doing so adds conformity with Git, but also simplifies the parser
which now only parse hex-hashes of a single valid length.
<csr-id-91c854e7b9f41738d0fde825cd474b8c00c1a49b/> remove winnow and replace it with hand-implemented parsers everywhere.
This will allow for simplified maintenance and editing (both human and machine)
down the road, and enable additional performance optimisations.
Parser compbinators to me ultimately were a failed experiment as I couldn't maintain them anyway, with it being too difficult for me to grasp and express everything in its very own kind of language, with a lot of different things to consider.
Note that this also removes detailed errors from all parsers that previously
used winnow, with the option to re-add those if there is demand.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
53f880c)gix_hash::Kind (d4439cd)5127973)winnow and replace it with hand-implemented parsers everywhere. (91c854e)4d5ba23)
</details>Strange - automatic release notes weren't generated or didn't arrive here. Have to look into that. Meantime, let's use the GitHub generated notes.
Strange - automatic release notes weren't generated or didn't arrive here. Have to look into that. Meantime, let's use the GitHub generated notes.
fuzzed_timeout on windows-11-arm by @EliahKagan in https://github.com/GitoxideLabs/gitoxide/pull/2619gix-pack by @cruessler in https://github.com/GitoxideLabs/gitoxide/pull/2602GIX_TEST_FIXTURE_HASH for gix-index tests by @cruessler in https://github.com/GitoxideLabs/gitoxide/pull/2598should_interrupt per entry in index_as_worktree by @sharifhsn in https://github.com/GitoxideLabs/gitoxide/pull/2631Full Changelog: https://github.com/GitoxideLabs/gitoxide/compare/v0.54.0...v0.55.0
<csr-id-672d7cd853fcb25223d750261aac4e4f0f8e528c/> accept owned AsKey inputs in raw setters
set_raw_value() and set_raw_value_filter() no longer requireconfig's'event` lifetime internally.
This makes the setter APIs consistent with the read-only raw accessors and allows short-lived key inputs, such as String-backed values, to be used without forcing an extra borrow at the call site.
Add a regression test covering short-lived keys passed to set_raw_value()
<csr-id-cf6c4035e40ca8790a010f4e268ffe51004eeecb/> allow &str to be parsed as key properly
Previously there were lifetime issue because the key
needed the same lifetime as the underlying parsed file,
which was hard to accomplish even with &'static str'
as it really needed "&'static &'static str".
However, this also means that owned keys can't be passed anymore.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
f9fbcba)a1ad31b)63b8419)e64e3b8)0396152)444a92b)package.include patterns more specific so they don't match ignored files (c2c917f)44020e0)9d04035)50fb46f)AsKey inputs in raw setters (672d7cd)af1ad55)&str to be parsed as key properly (cf6c403)29c275e)b1102c2)98bae84)
</details>gix dirwalk as a way to run gix-dir directly This is mostly for testing walks specifically, without needing them as part of gix clean or gix status.
gix dirwalk as a way to run gix-dir directly
This is mostly for testing walks specifically, without needing them as part
of gix clean or gix status.gix merge tree --message '' to allow creating commits
This is useful for controlling cherry-picks precisely.<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix dirwalk as a way to run gix-dir directly (add4cf4)gix merge tree --message '' to allow creating commits (6ab327e)
</details>sha1 and sha256 features to gix.
This way one can control which hashes are compiled in exactly,
while having reasonable defaults automatically.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
c389a2c)6183fd0)6bdb331)e8bf096)sha1 and sha256 features to gix. (3832916)gix-hash (e71c703)6a7287c)cargo machete CI job including exclusions (abd0724)f7277f3)
</details>This release was made to supersede the borked gix v0.82 release, as it released gix-actor as patch-update which broke v0.81 and probably earlier versi
This release was made to supersede the borked gix v0.82 release, as it released gix-actor as patch-update which broke v0.81 and probably earlier versions as well.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
ecf90fc)9327b73)
</details>4 commits contributed to the release over the course of 19 calendar days.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
d66ac10)8bceefb)7ce3c55)f7d0975)
</details>Progress report January 26 by @Byron in https://github.com/GitoxideLabs/gitoxide/pull/2393
gix-error conversions: gix-actor by @Byron in https://github.com/GitoxideLabs/gitoxide/pull/2396tracing instead of tracing-core to re-use the standard macros. by @Byron in https://github.com/GitoxideLabs/gitoxide/pull/2401core.bare being known or not by @Byron in https://github.com/GitoxideLabs/gitoxide/pull/2403blocking-http-transport-reqwest doesn't enable reqwest's default features by @fenhl in https://github.com/GitoxideLabs/gitoxide/pull/2404bytes to a fixed version by @Byron in https://github.com/GitoxideLabs/gitoxide/pull/2411gix-error by @Byron in https://github.com/GitoxideLabs/gitoxide/pull/2400imara-diff 0.2 in gix-blame by @cruessler in https://github.com/GitoxideLabs/gitoxide/pull/2420status work despite broken or invalid symlinks. by @Byron in https://github.com/GitoxideLabs/gitoxide/pull/2440Full Changelog: https://github.com/GitoxideLabs/gitoxide/compare/v0.50.0...v0.51.0
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
cbbdef5)562e684)0a333e5)c663b3f)7be8f90)211b4fb)
</details>4 commits contributed to the release over the course of 12 calendar days.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
Exn::into_box() to Exn::into_inner(). (939b8fc)exn to most pressing needs of gitoxide (abedade)
</details><csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
115e208)d6c5b9d)
</details>5 commits contributed to the release.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
21fecdf)f8435ea)6bf895c)93dd630)703644c)
</details>2 commits contributed to the release.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
82ff92f)fbf9c39)
</details>3 commits contributed to the release over the course of 1 calendar day.
<csr-id-6f469a6fea59c88e6c69a5f94b0bc8a5977cb75b/>
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
bdcce5f)doc_auto_cfg feature to fix docs.rs documentation. (6f469a6)3313233)
</details>allow credential fill with gix credential fill to run without a repo
gix credential fill to run without a repoRemove doc_auto_cfg feature to fix docs.rs documentation.
It is part of doc_cfg feature since https://github.com/rust-lang/rust/pull/138907
This fixes the docs.rs build
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix credential fill to run without a repo (924cd62)doc_auto_cfg feature to fix docs.rs documentation. (6f469a6)
</details><csr-id-6f469a6fea59c88e6c69a5f94b0bc8a5977cb75b/>
gix credential fill to run without a repo<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
Source::User now produces a directory even if HOME is not set.
This way it's easier to use downstream which may not have typical environment variables
set, particularly on Windows.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
89fb308)4da2927)b188a7d)6cc8464)9365cc3)838ff95)eee5199)888b763)10a20d6)Source::User now produces a directory even if HOME is not set. (042efa0)dc7343c)79ba9d0)202bc6d)d64f257)473fe52)428412c)784c046)
</details>add a gix commit sign prototype
gix commit sign prototypegix branch list<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix commit sign prototype (aacc326)gix branch list (58b5060)gix tag list when JSON is requested (fb2766b)
</details>gix commit sign prototypegix branch list<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
8699d0f)82f788e)gix commit sign prototype (aacc326)4da2927)6cc8464)gix-blame (a721e74)gix-blame (268dac4)525873f)04650a7)6651548)e537611)gix branch list (58b5060)c149116)gix tag list when JSON is requested (fb2766b)
</details>A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
Clippy helped 1 time to make code idiomatic.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
5a919c4)65037b5)dab97f7)a9a8ea1)dd5f0a4)554ce13)f8d7c0a)gix-config/gix-object benches to changes in criterion (91aef25)gix-config tests to changes in tempfile (eccd13a)151e3a5)648022b)f0ed2cc)c3f06ae)d2b4c44)8d4c4d1)
</details>3 commits contributed to the release.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
e104545)5f7f805)631f07a)
</details>add first debug version of gix tag list
add first debug version of gix tag list
gix revision list --long-hashes for faster iteration.
The performance of the short-hash generation was improved as well.
support for commitgraph list from..to to exercise the new 'hide' capability.
Enable precious file parsing in gix CLI by default, allow overrides.
That's pretty neat as one can now set GIX_PARSE_PRECIOUS=0 in the environment
to disable precious file parsing, good to see what difference it makes.
It's also possible to do this wiht gix -c gitoxide.parsePrecious=0.
add support for multiple blame ranges like gix blame -L <range> -L <other-range> ...
Update the blame subcommand to handle multiple line ranges. This allows specifying multiple -L options similar to the usage of git.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix tag list (37d3bf2)gix revision list --long-hashes for faster iteration. (ab52a49)gix-blame (4afc51d)commitgraph list from..to to exercise the new 'hide' capability. (c5bc49f)gix CLI by default, allow overrides. (1df1ebb)gix blame -L <range> -L <other-range> ... (36a6ffe)gix-blame (8143d69)
</details>File::section_ids() iterator and file::SectionMut::set_trust() #(1912)
That way it's easier to make changes to sections in a mutable instance of
Git configuration.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
Clippy helped 1 time to make code idiomatic.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
cc5b696)49fa9f3)db0b095)0bf84db)3b1bef7)c3c6504)6f009d7)46227e6)06bf1e1)359914c)File::section_ids() iterator and file::SectionMut::set_trust() #(1912) (aa91f9a)5823b22)Cargo.toml files in workspace to gix-features bump (6315536)b5e9059)68e6b2e)1612c73)fc5faf2)420e730)
</details>This is a bit empty as release notes got lost in a series of accidents, but it looks like it wouldn't have been too informative anyway.
This is a bit empty as release notes got lost in a series of accidents, but it looks like it wouldn't have been too informative anyway.
File::remove_section_filter()
The underlying issue isn't fixed, as ids in the lookup table remain even after deletion.
However, for now it was easiest to defensively access this data, while assuring that
the API (still) does what it claims.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
Clippy helped 1 time to make code idiomatic.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
File::remove_section_filter() (be80806)ada5a94)b41312b)38dff41)7b17da6), just before ) on same line in function calls (66a5ae1)01bd76d)16a248b)8e96ed3)503098d)11ac79c)fdc57e7)3cd3e2a)783c4e6)8df0db2)
</details>Add missing command docs + small style fixups Changes that affect the help/usage text shown at runtime:
<csr-id-f952c101cc8686e685074e8604e0f332c06d6767/> Add missing command docs + small style fixups Changes that affect the help/usage text shown at runtime:
Add descriptions for a few gix commands that didn't have it:
gix is-clean, gix is-changed, and gix env.
Add a description of the debug-only ein panic command.
Small spacing and capitalization improvements for consistency.
Add a line break in a /// block for brevity of the top line.
Changes to code style that do not affect what is shown at runtime:
Add . at the end of some /// first lines. (This doesn't
affect runtime behavior because clap normalizes this away.)
Put /// above all #[...] in a few places where it wasn't.
Adjust comment wrapping in a couple of places for clarity.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
<csr-id-f952c101cc8686e685074e8604e0f332c06d6767/>
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
<csr-id-17835bccb066bbc47cc137e8ec5d9fe7d5665af0/>
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
dea106a)1f6390c)7ec21bb)rust-version to 1.70 (17835bc)e8b3b41)
</details>add first 'debug' version of gix diff file
gix diff fileClippy helped 1 time to make code idiomatic.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix diff file (dbb1532)gix-blame (8a31d88)--since (330711d)gix-blame (e7084d8)hasconfig:remotes.*.url:<url-glob><csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
4000197)8ce4912)bc9d994)700cfa5)gix-packetline-blocking copy auto-generated (325588e)7a40648)0f0e4fe)c5955fc)hasconfig:remotes.*.url:<url-glob> (92558a1)gix dev-dependency. It's not really required. (581ef67)23034b0)db5c9cf)
</details>add gix env to print paths relevant to the Git installation.
gix blame -L start,endgix env to print paths relevant to the Git installation.gix blame to the CLI
That way it's possible to see the blame result of any file in the
repository.<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix blame -L start,end (4a78395). for consistency (ddddf02)gix env to print paths relevant to the Git installation. (75d689f)gix blame to the CLI (80e5804)
</details><csr-id-64ff0a77062d35add1a2dd422bb61075647d1a36/>
<csr-id-9c619e48db145928ff6ac420d6bb3d79deefc9f8/> make all filter arguments non-dyn.
Otherwise it can happen that &mut |section| {...} needs to be borrowed
for 'static, which makes it impossible to use.
The coercion seems to be messing with lifetimes.
<csr-id-17573779688e755a786546d5e42ab533088cd726/> remove all workspace dependencies The problem is that with them, we don't notice anymore if the crate changes, because a dependency changes. That also means that older versions of the dependency may stay even though some other crates might pick up a newer version.
Ultimately, this will lead to drift and subtle incompatibilities.
We declare this breaking to enforce a proper re-release.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
Clippy helped 1 time to make code idiomatic.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
3f7e8ee)48aa74b)9c619e4)795962b)507579e)64ff0a7)37c1e4c)af03832)72daa46)cdac4a9)22fbe70)fe1eb97)93e86f1)012a754)649f588)beba720)37ba461)2e0ce50)f992fb7)ec69c88)46cd1ae)1757377)
</details>add first 'debug' version of gix log It's primarily meant to better understand gix blame.
gix log
It's primarily meant to better understand gix blame.--tree-favor to gix merge tree|commit.
With it one can decide which side to favor in case of
irreconcilable tree-conflicts.gix merge file now uses THEIRS instead of OURS where needed<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix merge file now uses THEIRS instead of OURS where needed (0727b56)gix log (c7e04e9)gix-diff (960773e)--tree-favor to gix merge tree|commit. (471e046)A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
b3ff033)209b6de)
</details>3 commits contributed to the release over the course of 14 calendar days.
gix merge commit --debug
This yields additional debugging information with details about detected conflicts.gix merge commitsgix merge tree to merge trees similarly to git merge-tree.<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix merge commit --debug (0a5993f)gix merge commits (4a5afc7)gix (8d590f3)gix merge tree to merge trees similarly to git merge-tree. (84707c2)add Url::path_query_fragment()
Expose the decoded path, query pairs, and fragment of Git remote URLs
separately. Consumers can identify repository paths and inspect HTTP(S)
parameters without implementing scheme-specific splitting and decoding.
Recognize delimiters before decoding and reuse validated original spelling
to borrow decoded bytes. Preserve encoded separators, nested escapes,
ordered duplicate query keys, and literal percent text after construction
or mutation. Query pairs use form decoding (+ becomes space); SSH/SCP
paths, existing accessors, and serialization keep their behavior.
Reference Git's connect.c::parse_connect_url() and url.c at
1630431f326e. Use fetch-pack --diag-url to check SSH delimiters;
standalone url-parse does not model that transport.
migrate errors to gix-error
raise MSRV to Rust 1.88
The newly published dua-core 3.3 release used by linked-worktree removal
requires Rust 1.88, so raise every workspace crate and the advertised badge
together.
Keep the MSRV checks buildable by selecting the latest sysinfo and rusqlite
release lines that support Rust 1.88.
Url::path_query_fragment() (cd90fe1)A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
f2b522d)a65a17f)d19af16)0f25841)2e00b5e)unicode-bom (89d77dc)winnow a workspace dependency (78a7e32)1d37bf6)f5cd3ba)
</details>support for listing worktrees with gix worktree list
support for listing worktrees with gix worktree list
add first 'debug' version of gix diff tree.
It's primarily meant to better understand gix blame.
add new gix cat command.
It only prints things without fuzz.
Inspired by https://youtu.be/JYH5ILv5g1g?si=bHLBPFJiZyRUTl6u&t=211.
add gix merge-file with similar features as git merge-file
gix merge-base for the CLI
For now it only supports the standard merge-base, but more derivatives
can be added easily on demand.
gix clean warning and help for worktree fixgit clean options
-r/--repositories and --skip-hidden-repositories to make it
clearer what their relationship is, avoid creating the false
impression that repositories are never deleted in the absence of
-r/--repositories, and note that --skip-hidden-repositories
is sometimes needed to preserve not only separate repositories but
the (probably rarer) case of hidden nested worktrees of the current
repository.time to jiff
This swaps out time for jiff. It doesn't completely remove time
from the dependency tree. The last remaining use of time is in
prodash, outside of the gitoxide project.<csr-id-786bfec7c2cf25a68705b6ef09ba6390600742b8/> Unify style in config support info
This builds on b31d6b7 (#1531) by adjusting the capitalization and
quoting style of string arguments in progress.rs that help
document the status of what configuration options are and are not
planned.
Since I believe these strings are not usually rendered as Markdown, and most places that code formatting in Markdown would be used were already written with single quotes, this applies that quoting style consistently.
This applies initial capitalization, which was sometimes but not
always done. It does not apply a consistent style for when a
string will end in a ., which seems already to differ
deliberately for reasons of clarity. That can be adjusted later.
A small amount of minor rewording for clarity is also included.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix commit-graph is (49bca2a)gix diff tree. (0c554e0)gix cat command. (9c8bc03)gix merge-file with similar features as git merge-file (3da2da9)gix merge-base for the CLI (7249291)time to jiff (28ac657)gix clean warning and help for worktree fix (6eb4ea6)gix worktree list (c7213bc)
</details><csr-id-0dc2a0c467d2bee7f345c68a56e6c89ce10faf9c/> prevent newline amplification A fuzzer found input sized 780kb, but the output becomes 180MB in size, ultimately taking 48s to parse on M1 Pro.
Note that the parsing itself is fast, but we seem to modify the input in such a way that parsing takes way longer than it should. That might be another issue which it will probably find next, let's wait for it.
<csr-id-a9a3545db2b2cfa37f685666046c2ffd5f3fa806/> File::from_globals() now also provides options of the Git installation.
That way, it's usable for learning everything about credentials for example.
<csr-id-0ec2389e4e3c457f87cff2cbdd394a94f7d0d54a/> gix-config convenience initiative
A new gix_config::AsKey trait allows all gix_config::File methods
to receive an implementation of AsKey instead of the tuple of
(section, subsection, value_name). This is the default, and all
methods that take a tuple have been renamed to <name>_by(), note the _by suffix.
The terminology was reworked so that key is now only used to identify a value.
This change also affects the public API of gix, which provides
ways to set values on configuration snapshots which now by default
will only take a AsKey implementation.
Note that gix::config::tree::* keys now also implement AsKey,
which allows them to be used more conveniently when setting values,
too.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
Clippy helped 1 time to make code idiomatic.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
6232824)a1b73a6)0470df3)99c00cc)15f1cf7)mem::usage() expected peak (7dd58b8)ed66357)0dc2a0c)6c0364a)929744a)File::from_globals() now also provides options of the Git installation. (a9a3545)8d89b86)1dfa90d)tar files (dcab79a)5663a2c)gix-config convenience initiative (0ec2389)dbe1f22)9fa1054)2f9f0ac)acc1331)9c65d98)ea12fc2)68cbea8)2cefe77)8da55a3)2d0a352)
</details>resolve Windows directory symlink chains
resolve Windows directory symlink chains
Delaying symlinks until regular files are written is insufficient on
Windows: an early link can target another link that has not been created
yet. A single target probe then leaves a file link where a directory link
is required, making paths such as a-child -> z-dir/nested unusable.
Git for Windows retries unresolved links when directory links appear.
Add gix_fs::symlink::create_or_delay() and retry unresolved checkout
entries while other links make progress. When a pass makes no progress,
create the remaining dangling or cyclic links with the existing file
fallback.
Completed links need no removal or recreation. For forced overwrites,
try creation before unlinking so a deferred replacement leaves the
existing link intact if a later object error aborts checkout.
cap automatic macOS checkout at four workers
Using all logical cores for checkout causes APFS creation contention on
macOS. Benchmark fresh checkouts of the Linux tree to choose a default
that preserves throughput without starting unnecessary workers.
Resolve None and Some(0) to at most four available logical cores in
shared checkout plumbing, so clone, linked-worktree creation, and index
checkout inherit the cap. Positive explicit limits remain overrides;
other platforms retain their existing defaults, and builds without
gix-parallel/parallel continue to run on the calling thread. Update the
checkout.workers and clone documentation accordingly.
On an Apple M4 Max with 16 logical CPUs and native case-insensitive APFS,
the initial worker sweep measured median checkout times of 2.564 s at
four workers, 3.774 s at eight, and 6.874 s at automatic sixteen. An initial
probe using newer offline-resolved dependencies favored five workers,
but that advantage did not reproduce with the workspace's locked versions.
The final comparison using those locked versions covers every execution
order of four, five, and six workers, with six samples per setting:
| Workers | Median seconds | Range |
|---|---|---|
| 4 | 2.664813 | 2.533386–3.106756 |
| 5 | 2.665293 | 2.513454–2.938505 |
| 6 | 2.903967 | 2.843629–4.047406 |
Four and five split the paired wins three to three and have effectively
identical medians. Choose four to obtain the same measured throughput
with one fewer worker, matching the existing macOS removal cap.
A separate three-round comparison with the workspace's locked dependencies
checks the same collision-safe Linux tree against Apple Git 2.54.0. Rotate
execution order so each method runs first, second, and third once:
| Checkout | Median seconds | Range |
|---|---|---|
| Git, one worker | 7.293862 | 7.279254–7.394098 |
gix, one thread |
6.875375 | 6.822443–6.958276 |
gix, four workers |
2.376388 | 2.349792–2.493034 |
Git runs checkout-index --all --prefix=<fresh-destination>/ with
checkout.workers=1 against the prebuilt retained index. Its timer includes
process startup and index loading; gix times the checkout call with an
already loaded index. Index preparation, volume synchronization, complete
Git content/mode/symlink validation, and cleanup are outside both timers.
These are initial-checkout references, not timings of full clone or branch
switch workflows. No builds or tests overlap the timed samples.
Raw wall seconds in execution order:
gix/1 6.822443, gix/4 2.376388.gix/4 2.493034, Git 7.279254, gix/1 6.958276.gix/1 6.875375, gix/4 2.349792, Git 7.293862.All nine checkouts pass Git content verification. This is a separate run
from the four/five/six comparison above; compare methods within each run.
A separate four-pair run compares Apple Git 2.54.0 with
checkout.workers=3 and checkout.workers=4 on the same retained tree,
using checkout-index --all --prefix=<fresh-destination>/ as above.
Alternate execution order between rounds:
| Git workers | Median seconds | Range |
|---|---|---|
| 3 | 4.261867 | 4.058227–4.361033 |
| 4 | 3.745698 | 3.611599–3.768478 |
Four workers win all four pairs; three offers no advantage here. A
separate warmup with GIT_TRACE2_EVENT confirms four checkout--worker
processes; exclude that traced 3.367775 s sample from the timing table.
All eight untraced checkouts pass Git content, mode, and symlink checks.
Volume synchronization, validation, and removal remain outside timers;
no probe compilation overlaps these measurements.
Raw wall seconds in execution order:
This later run measures Git's worker scaling. The earlier one-worker Git
and gix figures are reference timings from their own run, rather than
additional matched samples in this comparison.
Borrow objects read-only from the bare Linux repository at
/Users/byron/dev/git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux,
commit 707df3375124b51048233625a7e1c801e8c8a7fd. Use independent metadata
and fresh destinations under /private/tmp, omitting thirteen later
case-fold collisions that native APFS cannot represent. The retained tree
contains 88,821 entries, including 79 symlinks, and 1,509,611,994 blob bytes.
Time only checkout; synchronize the volume, verify content, executable
modes, and symlinks against isolated Git, and remove destinations outside
the timer. No builds or tests overlap timed samples. Keep the benchmark
method and decisive measurements in this commit message.
These warm-cache initial-checkout results cover one Mac and one volume.
They do not establish an optimum for every filesystem, repository, filter
pipeline, or incremental checkout. Explicit worker limits remain available
for those workloads; no cold-cache or durable-write benchmark was made.
mailmap check similar to git check-mailmap.
That way it becomes a little easier to maybe try out other special cases
in the wild.gix clone with --ref support.
--ref is similar to --branch, but was renamed as it also supports
tags for example.<csr-id-202f3e48a96b38d32b11d28449358c7d1f3546ff/> Make it easier to compile gitoxide as dynlib
And also optimize compilation time: By making plumbing and porcelain
as modules the lib.rs, they can be compiled after the rmeta for the
dependencies are generated.
For the uni.rs which uses both plumbing and porcelain, this would avoid
compiling these two modules twice.
Clippy helped 1 time to make code idiomatic.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
mailmap check (3e08fa3)mailmap check similar to git check-mailmap. (2a56387)gix clone with --ref support. (9bf01e4)src/plumbing/main.rs (4596a39)preserve allocation failure sources
rubberstamp
Keep the original TryReserveError inside the OutOfMemory I/O error so structured classification can distinguish allocator failure without treating malformed stream metadata as corruption.
raise MSRV to Rust 1.88
The newly published dua-core 3.3 release used by linked-worktree removal
requires Rust 1.88, so raise every workspace crate and the advertised badge
together.
Keep the MSRV checks buildable by selecting the latest sysinfo and rusqlite
release lines that support Rust 1.88.
A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
4f98e94)9511416)d6cd449)cd4de83)04ef31e)gix-pack (bad5b48)
</details>3 commits contributed to the release over the course of 1 calendar day.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
Clippy helped 1 time to make code idiomatic.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
095c673)5755271)55f379b)f72ecce)b590a9d)7f6bee5)45edd2e)52efa90)0ce06a6)a5168aa)
</details>This release contains fixes relevant to the safety of checkouts:
This release contains fixes relevant to the safety of checkouts:
checkout respects options for core.protectHFS and core.protectNTFS.
This also adds gitoxide.core.protectWindows as a way to enforce
additional restrictions that are usually only available on Windows.
Note that core.protectNFS is always enabled by default, just like
it is in Git.
more robustness in the face of a trampling-herd of threads loading a single index. The motivating example is here: https://github.com/praetorian-inc/noseyparker/issues/179
Previously, it was possible for a trampling herd of threads to consolidate the disk state. Most of them would be 'needs-init' threads which could notice that the initialization already happened, and just use that.
But a thread might be late for the party and somehow manages to not get any newly loaded index, and thus tries to consolidate with what's on disk again. Then it would again determine no change, and return nothing, causing the caller to abort and not find objects it should find because it wouldn't see the index that it should have seen.
The reason the thread got into this mess is that the 'is-load-ongoing' flagging was racy itself, so it would not wait for ongoing loads and just conclude nothing happened. An extra delay (by yielding) now assures it either seees the loading state and waits for it, sees the newly loaded indices.
Note that this issue can be reproduced with:
'./target/release/gix -r repo-with-one-pack -t10 --trace odb stats --extra-header-lookup'
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
core.protectHFS and core.protectNTFS. (886d6b5)Store::at() where possible (17fea2a)replace fs with gix-fs
gix-fs already provides the filesystem helpers and recursive walkers.
Keeping their duplicate implementation in gix-features adds unnecessary
filesystem dependencies to the foundational feature crate.
Remove the fs module and the walkdir and fs-read-dir features. Migrate
workspace callers to gix_fs, move traversal requests to gix-fs/walkdir,
and update the manifests, lockfile, traversal documentation, and feature
check script together.
fs with gix-fs (cf1ba49)A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
b050327)52c3bbd)3e5c974)f8ce3d0)e09a4ec)e5f815a)29e470b)819d7eb)b3556b2)096fd12)ba3bf65)6281e1a)
</details>add gix status --ignored support
add gix status --ignored support
add gix status --index-worktree-renames
This enables rename-tracking between worktree and index, something
that Git also doesn't do or doesn't do by default.
It is, however, available in git2.
gix status with submodule and rewrite support.
Submodule changes are now picked up as long as the submodule is
in the index.
Further, it's possible to enable rename-tracking between
index and worktree separately.
add gix is-clean|is-changed
It's a good way to compare the time it takes to run a full status
compared to a quick is-dirty check.
gix submodules list --dirty-suffix for dirty-information
This is a submodule-centric and greatly simplified way of obtaining
describe information with dirty-suffix.
Note that status information is also possible, but it seems
hard to display nicely, which this command isn't great at
in the first place.
add gix commit describe --dirty-suffix
That way a suffix will be added depending on the dirty-state of the repository.
gix status --format to communicate the current format is very simple. (23bea36)gix status --ignored support (84c74ff)gix status --index-worktree-renames (66e87cd)gix status with submodule and rewrite support. (61c002b)gix is-clean|is-changed (98b3680)gix submodules list --dirty-suffix for dirty-information (afd20ca)gix commit describe --dirty-suffix (58231b4)migrate errors to gix-error
raise MSRV to Rust 1.88
The newly published dua-core 3.3 release used by linked-worktree removal
requires Rust 1.88, so raise every workspace crate and the advertised badge
together.
Keep the MSRV checks buildable by selecting the latest sysinfo and rusqlite
release lines that support Rust 1.88.
A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
Clippy helped 1 time to make code idiomatic.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
45b4470)f2e111f)a663e9f)e175b20)516e105)face359)ae86a6a)53e9b4e)13d5602)7b44c7f)8430442)69cb78b)b7ca4b2)9470554)b8cba96)3edf0fe)
</details>add gix clean --patterns-for-entries|-m to help with wildcards.
gix clean --patterns-for-entries|-m to help with wildcards.gix clean<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
-n argument as no-op to make them more compatible. (8959b21)gix clean --patterns-for-entries|-m to help with wildcards. (9863d75)gix clean (e8597f3)<csr-id-b382f76a4ace08a6e743b292c4f2c383dfd94e8f/> assure excessive amounts of newlines can't lead to amplification. Now we won't read more than 1024 newlines in a row, which leads to a protection from specifically crafted configuration files which can amplify themselves when large amounts of edits happen on them.
If somebody where to create a lot of sections based on one that has a huge amount of newlines before it, this whitespace would be retained with each new section, causing huge files to be created in memory that cause great delays when writing the file back and re-reading it.
Maybe there would have been a way to avoid copying excessive amounts of whitespace when altering a section, or maybe one could also have adjusted the fuzz-test that found it [1]. This would, however, have been much harder and time-consuming to implement for dubious value.
<csr-id-c71d16e45ea4ed68b76a43a7ed653d73f3672878/> greatly reduce peak memory usage when reading files. Previously it was possible to cause a memory consumption of 2.5GB by merely reading a specifically tuned configuration file sized a little less than 1MB, a massive 2500x amplification.
Data structures have been optimized and premature optimizations removed in favor of much more efficient memory usage.
Now the same file causes a 36MB peak memory usage, still quite a lot, but also ~70x less than before.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
eb6aa8f)6a2e0be)4138902)b6c04c8)b382f76)17a81c7)6bb407f)c71d16e)36f4d92)34e4a16)2420547)9cdb461)
</details>5 commits contributed to the release.
<csr-id-3bd09ef120945a9669321ea856db4079a5dab930/>
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
972241f)8c492d7)rust-version manifest field back to 1.65. (3bd09ef)ce44fe3)fee6bde)
</details>Add rev parse --reference. It's similar to git rev-parse --symbolic-full-name.
rev parse --reference.
It's similar to git rev-parse --symbolic-full-name.mark gix::interrupt::init_handler() as unsafe
The passed interrupt() argument will be called from a signal
handler, so that needs to be documented and the call sites need to
state that they fulfill the contract.
Thanks to @Manishearth for pointing this out.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
rev parse --reference. (193ffcd)gix::interrupt::init_handler() as unsafe (59b8104)
</details><csr-id-aea89c3ad52f1a800abb620e9a4701bdf904ff7d/> <csr-id-14460020ff5f5c6f1d5c4089d35d7d6932604d14/> <csr-id-ebc051c1d470bbb063deb9ff57ba058b93f1e8a3/>
GIT_CONFIG_NOSYTEM is treated as boolean.
That way, it can also be deactivated, which is exactly what git
does.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
Clippy helped 1 time to make code idiomatic.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
e1aae19)e78a92b)4454c9d)aea89c3)d38d1cc)7ddf948)f89e6c4)0f71709)27490d9)c6d1635)b6d4e99)75f48d6)90219cd)7917c13)file_section test in favor of integrating reasonsable tests with file. (64a4a75)1446002)ebc051c)f5a0296)8053710)1691ba6)c1cfe6e)7549559)35439de)ff1542c)GIT_CONFIG_NOSYTEM is treated as boolean. (1fe600e)
</details>GIT_CONFIG_NOSYSTEM now also affects the installation directory. It makes sense to consider it part of the 'system', and allows for proper isolation o
<csr-id-6738955949d82a66c070dcb65e368652898bd1d2/> GIT_CONFIG_NOSYSTEM now also affects the installation directory.
It makes sense to consider it part of the 'system', and allows for proper
isolation of gix operations, for example in tests.
This is also a fix, as previously it checked for ...NO_SYSTEM, instead of NOSYSTEM.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix rev parse --format to provide different versions of the same content. This only applies to blobs, but allows to obtain different versions of the s
gix rev parse --format to provide different versions of the same content.
This only applies to blobs, but allows to obtain different versions of the same blob
like:
--trace mode, greatly increase message-buffer size.
That way, it's much less likely that messages will get lost
due to being overwritten before they can be displayed every
100ms or so.GITOXIDE_* environment variables to GIX_#<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
GITOXIDE_* environment variables to GIX_# (2189cee)gix rev parse --format to provide different versions of the same content. (cf51a4d)gix-diff (1706e23)diff::resource_cache() low-level utility for rapid in-memory diffing of combinations of resources. (4aea9b0)fsck connectivity into just fsck much like git fsck (7ab5c76)--tree-style raw. (8dfbb4b)-c options are given on the command-line. (f9ae1bc)--trace mode, greatly increase message-buffer size. (b230078)gix free discover to inform about repository discovery. (886289f)A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
55d386a)d3dcbe5)winnow 0.5.24 (abcfb65)51c7abc)5a0d93e)bb3224c)c0e72fb)b65a80b)
</details>This release includes an overhaul of the url parsing implementation, allowing more urls to be parsed correctly and refining the error messages for inv
This release includes an overhaul of the url parsing implementation, allowing more urls to be parsed correctly and refining the error messages for
invalid ones. Improvements include the added support for ssh aliases (github:byron/gitoxide has previously been parsed as local path), adjustments
around the interpretation of colons in file names (previously we disallowed colons that were not followed up with a slash character) and some smaller
changes that bring the interpretation of file urls more in line with Git's implementation.
There are still many (edge) cases in Git's url parsing implementation which are not handled correctly by Gitoxide. If you notice any such deviation please open a new issue to help us making Gitoxide even more correct.
gix status auto-writes changed indices.
This prevents expensive operations to re-occour.gix status -s/--statistics to obtain additional information on what happened.
This is useful for understanding performance characteristics in detail.<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix status auto-writes changed indices. (46e5919)gix status -s/--statistics to obtain additional information on what happened. (7ba2fa1)
</details>A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
Clippy helped 1 time to make code idiomatic.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
68e5432)1347a54)345712d)
</details>This release contains a security fix which assure URLs like 'ssh://-oProxyCommand=open$IFS-aCalculator/foo' will not execute attacker-controlled strin…
This release contains a security fix which assure URLs like 'ssh://-oProxyCommand=open$IFS-aCalculator/foo' will not execute attacker-controlled
strings. The above can, on MacOS, launch the calculator app when using it with gix clone for example, up to v0.29.0.
gix status with basic index-worktree comparisongix free index from-list and gix index from-tree gain --skip-hash.
This flag can be derived from options, but thus far we have no higher-level
writing of the index so this has to do to see the difference in performance.ein and gix now share some code via the gitoxide library.
This can slightly improve compile times as well, even though it wasn't measured.prodash
It makes proper usage of Progress types easier and allows them to be used
as dyn traits as well.dyn trait where possible.
This reduces compile time due to avoiding duplication.Clippy helped 1 time to make code idiomatic.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
ein and gix now share some code via the gitoxide library. (d3ac691)gix status with basic index-worktree comparison (f094f71)dynification (f658fcc)dyn trait where possible. (072ee32)prodash (ed327f6)gix-index and pass skip-hash through for performance.. (713cd59)gix free index from-list and gix index from-tree gain --skip-hash. (3ff5ac0)index.skipHash (773b6e3)
</details><csr-id-db0c4017142fd25d26d1c6860972b1ac84b24a6e/>
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
7891fb1)8a60d5b)9c528dc)db0c401)
</details>gix submodule subcommand for simple submodule listing and information retrieval
gix submodule subcommand for simple submodule listing and information retrievalgix index entries --recurse-subomdules to also list submodules.gix index entries with styles and pathspecs.
This adds support for more simple git style, which is faster and thus
allows for more direct comparisons to git ls-files.gix commit verify-signature to do something akin to git ... --show-signature.<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix submodule subcommand for simple submodule listing and information retrieval (1ccbe16)gix index entries --recurse-subomdules to also list submodules. (6bc69e3)gix (ca972a2)Defaults::from_environment() when parsing pathspecs. (2a99034)gix index entries (22477bd)gix index entries with styles and pathspecs. (c30ac0c)gix (a201f0d)gix commit verify-signature to do something akin to git ... --show-signature. (cd6cfe4)gix-archive (feba76d).gitmodule file abstraction (6a2e6a4)
</details>log dependency in favor of gix-tracedyn trait where possible.
This reduces compile time due to avoiding duplication.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
Clippy helped 1 time to make code idiomatic.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
8bd0456)375db06)6135a5e)gix usage for faster compile time (9d33e2f)log dependency in favor of gix-trace (2b8d09f)dynification (f658fcc)dyn trait where possible. (072ee32)5044c3b)363ee77)
</details>8 commits contributed to the release over the course of 29 calendar days.
gix archive<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix archive, which is where it should shine. (567b1a4)gix archive (32bbb8b)<csr-id-ef54aab9e5521add4154ee8d902d62612a9d8d4a/>
<csr-id-c51c8daee1ab54130ae3ed83ce67d08f01c4881a/> fix incorrect s/git-config/gix-config/ 3a861c8f049f6502d3bcbdac752659aa1aeda46a just blindly replaced any occurence of "git-config" or "git_config" with "gix-config"/"gix_config".
There is no such thing as a gix-config file. gix-config is a git-config file parser.
<csr-id-66dadf807f41aa9e828639c52a7d220bf4f3df72/> regression that could cause non-linear parsing behaviour.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
30b2761)f23ea88)8f3f358)73c685a)0d258f4)nom to winnow in remaining uses in gix-object, gix-ref, and gix-actor for ~20% more performance. (ef54aab)winnow to latest patch release (8c41848)7735047)c51c8da)66dadf8)a743c5d)0f9af3f)5366f79)e208362)3f8c91f)ee75de1)510192e)
</details>This release fixes a possibility for V1 fetches to deadlock if negotiation would span multiple rounds (see issue #882) for details.
This release fixes a possibility for V1 fetches to deadlock if negotiation would span multiple rounds (see issue #882) for details.
gix level.
This is merely a debug tool to learn about generation numbers.
All commit-graph commands now operate on a repository.gix --trace to also print tree-like instrumentation
gix fetch --open-negotiation-graph[=limit]
Open the negotiation graph as SVG, after optionally specifying a limit
as rendering/layouting can be very slow.
It's useful to see how the negotiation algorithm is reasoning about each commit.
gix fetch --negotiation-info to provide additional information about the negotiation phase.
bit revision list --svg to create a visual graph of commits.
It's mainly a test of how well layout-rs performs.
clippy::redundant-closure-for-method-calls lintClippy helped 1 time to make code idiomatic.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gitoxide publishable again (c16b1df)corpus --dry-run and --task-sql-suffix and --repo-sql-suffix (4cef57d)gix-trace (bd6e3d7)gix --trace to also print tree-like instrumentation (c494cfd)gitoxide version according to what's in git (83f6466)gix fetch --open-negotiation-graph[=limit] (452ed6b)gix fetch --negotiation-info to provide additional information about the negotiation phase. (096838f)gix docs available when using cargo doc (518159d)bit revision list --svg to create a visual graph of commits. (bd32e39)clippy::redundant-closure-for-method-calls lint (bcad5c2)gix level. (b82edc8)gix config tree (7aaaebf)
</details>File::push_section() is now infallible.
Previously it used a Result even though it couldn't fail anywhere.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
4604f83)gix-submodule (f3c4311)b629f8a)File::push_section() is now infallible. (d091c78)6b4a303)ef8ccd9)
</details>Allow ObjectId, oid, ChangeId, Prefix, HexDisplay, and ReverseHexDisplay to compare with str and String values without allocating, reusing the existin
compare hash types with text
Allow ObjectId, oid, ChangeId, Prefix, HexDisplay, and ReverseHexDisplay to
compare with str and String values without allocating, reusing the existing
stack encoders and Kind::hex_buf().
Make full object and change ID comparisons symmetric but intentionally less
lenient than parsing: only their exact canonical lowercase spelling compares
equal. Uppercase input remains parseable, but treating differently-cased strings
as equal through the same hash would violate PartialEq transitivity even though
the strings differ from each other.
Keep Prefix and truncated display comparisons directional, with the hash value
on the left, because their text omits the hash kind or remaining digest and
therefore cannot uniquely identify the structural value. This prevents distinct
hashes from forming non-transitive equality chains through a shared textual
prefix.
The parsing switches from nom to winnow, which eases maintenance and improves performances.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
231ac1c)db63815)e4d2890)daf3389)224121b)1a1e2f5)beac408)63552ee)8db009c)fe997c8)8581d25)9e6ba0f)b790948)5fc1096)083efbc)5f2b68e)0fe3854)d2e06c8)edb4e04)bdcd379)42ae766)b0287a8)a639994)cfc642a)18bee03)6ac1b37)5b3ae94)3d9ae21)
</details>A maintenance release without user-facing changes.
A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
The main attraction of this release is support for multi-round negotiations thanks to support for the standard negotiations algorithms. Further, gix i
The main attraction of this release is support for multi-round negotiations thanks to support for the standard negotiations algorithms.
Further, gix index entries now lists attributes as well, and there is the new gix attribute query sub-command in the vain of git check-attrs.
gix attributes validate to validate attributes and ignore against git as baseline.
Use this command to test the entire index for ignored paths and their attributes and use
git check-attr and git check-ignore to validate that git agrees. Collect all
mismatches and print them.--statistics for gix excludes query
With it one gets some insights into the work done to fulfil the query.gix attribute query as something similar to git check-attrs.no-repo index from-list to create an index with empty files from the given list.
The list could be created with find . -type f for example.gitoxide on docs.rs<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
just fmt (ffc1276)gix (7983f6f)gix attributes validate to validate attributes and ignore against git as baseline. (e1fcc7f)--statistics for gix excludes query (450b232)gix attribute query as something similar to git check-attrs. (bfdcb14)no-repo index from-list to create an index with empty files from the given list. (b8db207)gitoxide on docs.rs (13a0f1e)jwalk to have a better comparison. (d67551d)
</details>A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
Clippy helped 1 time to make code idiomatic.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
68ae3ff)c70e54f)e4dded0)3ef32af)
</details>A maintenance release without user-facing changes.
A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
69c6a36)c143cf4)gix-path across all crates (73c1292)
</details>A maintenance release without user-facing changes, just to fix installation
A maintenance release without user-facing changes, just to fix installation
A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
27e8c18)00f96fb)285ce12)
</details>gix index entries also prints attributes.
gix index entries also prints attributes.gix clone and gix fetch with controls for shallow repositories.ein t trace-path know accepts the trace-file alias.stdout on each write, now this is done only once.gix free index entries into gix index entries.<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix index entries also prints attributes. (08e8fc2)gix free index entries into gix index entries. (ca8ebdf)gix-worktree (13a070f)index.skipHash (f29f35c)gix clone and gix fetch with controls for shallow repositories. (9723e1a)ein t query (d5616b6)ein t trace-path know accepts the trace-file alias. (f93e964)
</details><csr-id-bcad5c22049d56a25ef69d6c7a3344e78f9a1d4d/>
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
ea9f942)18b0a37)aa16c8c)4f635fc)fe59956)clippy::redundant-closure-for-method-calls lint (bcad5c2)
</details>This release adds the new ein tool query analytics engine, which maintains a database of a git repository as acceleration data structure to run useful
This release adds the new ein tool query analytics engine, which maintains a database of a git repository as acceleration data structure to run useful queries on.
It's nothing more than an MVP, and was inspired by a program to accelerate Git-Heat-Map.
ein tool query - a git analytics engine.
A tool to build and efficiently maintain a database of information contained
in a git repository, preferably the kind of information that is expensive to obtain,
in order to facilitate queries that would be prohibitive without an accelerating
data structure.gix tree entries with rev-spec support.
Previously it wanted a tree-id, now it can derive it itself.<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
ein tool query - a git analytics engine. (f8cc623)gix tree entries with rev-spec support. (49520d1)<csr-id-dbc6cbb4363c2532f81b0bd6e351c4577bb9e9a3/>
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
9a9fa96)8f15cec)420553a)2578e57)dbf8aa1)4795fcf)3ef5c90)279dc09)dbc6cbb)13e01f5)
</details>make docs-rs work, and publishing
add rename() for replacing read-only fixture files
I removed a lot of tests for that, assuming it's trivial enough to get right
and existing tests that use it are proof of function enough.
Git creates read-only commit-graph files. On Windows, this also prevents
replacing them with std::fs::rename(), requiring fixture setup to clear
the destination's read-only attribute first.
Add gix_testtools::rename() to retry permission-denied renames after
clearing that attribute. Other platforms retain std::fs::rename()
behavior. Document that callers must use writable fixtures or fixture
initialization and release memory mappings before replacing backing files.
Trace Bash fixture commands without changing captured baselines
A flaky Windows fetch test failed while generating make_remote_repos.sh,
before the worktree assertions ran. The fixture output stopped after cloning
credential-helpers, leaving no failing command or process exit status to
explain the abort. Expected merge conflicts earlier in the script further
obscured where setup actually failed.
Enable set -x by default for .sh fixtures on Bash 4.1 and newer. Route
traces through BASH_XTRACEFD to a duplicate of the original stderr, so
commands that redirect stderr into fixture baselines do not capture tracing
output. Keep successful fixture generation quiet by retaining the runner's
existing policy of printing captured output only on failure.
Bash 3.2, including the version shipped with macOS, cannot redirect xtrace
independently of stderr. Use an inherited ERR trap there to report the
failed command, script location, and status through the same descriptor.
Include the subprocess exit status in the runner's error on every platform.
Add coverage for silent command lookup failures, unchanged redirected stderr
baselines, and exit statuses in fixture errors. This improves diagnosis; it
does not identify or fix the original Windows flake.
add symlink preflight for Bash fixtures
Careful refackiew, only the tests were mostly waved through as they
are known to be super thorough. Only their style needs checking, which
was fine here.
Fixtures that require symbolic links need to distinguish unavailable symlink
creation on the host from broken fixture setup. Otherwise, tests either fail
on unsupported filesystems or risk hiding unrelated errors when skipping.
Inject gix_testtools_require_symlinks into Bash fixtures to probe creation
of a real link before generating contents. Record the outcome at the fixture
root and stop successfully when links are unavailable. Tests can then use
fixture_has_symlinks() to skip explicitly; missing or malformed results,
unexpected ln exits, copied files, and later setup failures remain errors.
Preserve script arguments and Bash 3.2 source context without exporting the
helper to child shells. Include the prelude in cache keys for fixtures using
the probe, and document archive and writable-fixture constraints.
redact unstable values in diagnostic snapshots
Complete error snapshots expose useful context and causes, but temporary
paths, dynamically assigned ports, object IDs, and platform-specific I/O
messages make their output unstable.
Add redact_debug_snapshot() to apply explicit replacements, reuse object-ID
normalization, and render OS errors by their portable ErrorKind. Handle
plain and debug-escaped Windows paths while retaining meaningful suffixes
and unrelated backslashes. Return an owned Debug value so insta displays
the diagnostic without additional quoting or newline escaping.
Cover redaction, object identity, and OS error formatting, and convert the
environment, SBOM argument, and Rust fixture error assertions to complete
inline snapshots. The helper is available before downstream diagnostic
snapshot migrations need it.
Make checkout safety fixtures reliable on Windows
The traversal fixture rewrites .git/index to install paths Git would not
normally accept. MSYS sed reads that binary index in text mode, removing
carriage returns from incidental CRLF bytes in its stat data. Variable
timestamps make the resulting corruption intermittent. Setting the mtime to
2000-11-01T12:31:06Z (0x3a000d0a) reproduced the reported
U git/hooks/pre-commit and unresolved-conflict error exactly.
Use Perl with binary standard streams and literal path substitution, which
also works on systems without sed -b. Keep the CRLF-containing timestamp
in every generated repository so text-mode index corruption is exercised
deterministically by the existing checkout safety tests.
The same log's long-path warnings come from a relative XDG_CONFIG_HOME
being reinterpreted after the fixture changes directories. Make the isolated
configuration path absolute, and exercise both absolute and relative fixture
roots by checking that Git still reads the intended attributes after cd.
Validated on Windows with Git 2.55.0.windows.3:
Keep rust workspace tests inside disposable repositories and isolated environments
Direct Git launches inherited repository selectors and user configuration even
when tests supplied a fixture working directory. Tests of default-environment
APIs and local Git transports also shared the runner's environment. A few
journey tests wrote beneath source directories or used the source checkout as
the repository under test.
Use the shared gix-testtools Git command builder for subprocess setup, isolated
repository options for fixtures, and isolated child processes where the real
environment-reading API must be exercised. Scope CWD changes, copy the fixture
used by an object-write test, and run shell journeys through jtt run. Keep
journey worktrees and example output within their disposable sandboxes and
replace the attributes checkout test with a representative fixture repository.
Prompt examples also run in isolated children and must build successfully; the
old tests could ignore build failures and execute stale cached binaries.
The affected Rust crate suites, internal test-tool build, and max-pure journey
suite pass from a source copy without Git metadata. Signing and Git-daemon
checks use only disposable keys, repositories, and local sockets.
isolate fixtures from inherited Git templates
Fixture commands already ignore external Git configuration, but inherited
GIT_TEMPLATE_DIR could still inject personal template files into repositories
created by git init, making fixtures depend on the caller's environment.
Clear that variable in the shared command setup used by fixture scripts and
isolated Git helpers. Keep Git's installed templates available because existing
fixtures rely on their standard files and directory layout.
Document the isolation behavior and add a regression that supplies an external
template containing a marker file, then verifies that git init does not copy
it into the fixture repository.
keep fixture scripts isolated when they set GIT_CONFIG_COUNT themselves
The isolation configuration (no signing, no auto-maintenance, init.defaultBranch=main)
reached scripts only as GIT_CONFIG_COUNT variables, so a script exporting its own
GIT_CONFIG_COUNT replaced all of it. With maintenance back on, each commit in such a
script spawned a detached git maintenance run --auto that could outlive the script and
mutate the fixture while it was being copied, failing tests with a bare ENOENT.
tests/fixtures/generated-do-not-edit/, written once per process; a script's ownGIT_CONFIG_COUNT layers on top of itGIT_CONFIG_COUNT is removed from the script environment, as it used to begit() call that writes global configuration fails with a clear messageraise MSRV to Rust 1.88
The newly published dua-core 3.3 release used by linked-worktree removal
requires Rust 1.88, so raise every workspace crate and the advertised badge
together.
Keep the MSRV checks buildable by selecting the latest sysinfo and rusqlite
release lines that support Rust 1.88.
rename() for replacing read-only fixture files (9af9145)jtt (40b8e5e)A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
git-protocol to gix-protocol (823795a)git-features to gix-features (e2dd68a)git-repository to gix (7bed2a9)A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
7ebc9f7)0135158)43ebaf2)
</details>gix clone is now permitted without specifying a destination directory. Note that the implementation doesn't take into account potential redirects and
gix clone <url> is now permitted without specifying a destination directory.
Note that the implementation doesn't take into account potential redirects and renames
as it's implemented only with the first URL it sees (not the redirected ones).http.schannelCheckRevokeClippy helped 2 times to make code idiomatic.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix clone <url> is now permitted without specifying a destination directory. (b81f650)gix progress now usees the configuration tree as basis for data. (ea76bf5)tabled (7aed326)ssh related configuration variables. (3f91088)home in env::home_dir()gix-path for obtaining some shared directories as base for path generation.
This will make system wide configuration available on windows at least when using the migw builds.<csr-id-b83ee366a3c65c717beb587ad809268f1c54b8ad/> Rename serde1 cargo feature to serde and use the weak-deps cargo capability.
With it it's possible to not automatically declare all optional dependencies externally visible
features, and thus re-use feature names that oterwise are also a crate name.
Previously I thought that serde1 is for future-proofing and supporting multiple serde versions
at the same time. However, it's most definitely a burden I wouldn't want anyway, so using
serde seems to be the way to go into the future.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
serde1 cargo feature to serde and use the weak-deps cargo capability. (b83ee36)91134a1)30a1a71)74cb5ee)home in env::home_dir() (13edfe9)8dbd0a6)cdef398)19338d9)23ee47f)3d47919)gix-path for obtaining some shared directories as base for path generation. (da9009f)d0052c1)f9ad837)6932017)
</details>8 commits contributed to the release over the course of 3 calendar days.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
38eed1d)d47cebe)d1e5e12)d1bd513)02c4659)cc48c35)e965b18)877951a)
</details>This release also fixes compatibility issues that formerly prevented to fetch or clone form https://googlesource.com.
This release also fixes compatibility issues that formerly prevented to fetch or clone form https://googlesource.com.
GIT_(COMMITTER|AUTHOR)_(NAME|EMAIL|DATE) with git configuration.
That way it becomes more obvious where values are coming from.auto-enabled verbosity for gix fetch/clone and add --no-verbose.
I found myself always adding (and having to remember to add) the -v flag
for long-running operations so these should be able to default to a
higher verbosity level.
To counter that, there is a new --no-verbose flag to turn that off.
add --strict option to enforce strict checking of configuration.
gix odb stats to calculate statistics on the object database.
This includes the amount of objects along with a listing of where they are
located.
gix clone --no-tags support.
This is the same as git clone --no-tags.
open::ReplacementObjects is removed in favor of two custom git-configuration flags.
Now it's possible to map the environment variables GIT_REPLACE_REF_BASE and GIT_NO_REPLACE_OBJECTS
to custom git configuration keys which can also be set, namely gitoxide.odb.replaceObjectsRefBase
and gitoxide.odb.noReplaceObjects.
Along with the possibility of disabling the usage of GIT_ prefixed environment variables one
reaches the previous level of control without making object replacement a special case.
represent object cache configuration like GITOXIDE_PACK_CACHE_MEMORY in git-configuration.
That way there is a unified system for how to set values, which may be overridable by configuration
variables or not.
With this changes, the explicit application of environment variables for setting the cache isn't required anymore as everything happens using git-configuration, and automatically, while providing full control like before.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
ein t estimate-hours command (4c93de1)gix odb stats to calculate statistics on the object database. (8c9c243)gix clone --no-tags support. (e2b8c5d)gix progress to inform about remote.<name>.tagOpt (3ebb340)gix fetch/clone and add --no-verbose. (9814369)atty to is-terminal (7304bc1)git-repository (c4f68bf)GITOXIDE_PACK_CACHE_MEMORY in git-configuration. (becbd8d)GIT_(COMMITTER|AUTHOR)_(NAME|EMAIL|DATE) with git configuration. (a4ac9cf)open::ReplacementObjects is removed in favor of two custom git-configuration flags. (49f39d6)git-repository (f1a4c8b)--strict option to enforce strict checking of configuration. (aeb4a1d)git-config (1c2e755)allow requiring archived scripted fixtures
Add version-aware fixture loaders:
scripted_fixture_read_only_with_git_version()scripted_fixture_read_only_with_args_with_git_version()Both use normal fixture generation when the installed Git version satisfies
the caller-provided predicate. For incompatible versions, they require an
identity-matching archive, ignore GIX_TEST_IGNORE_ARCHIVES, and return None
instead of running the fixture script when no usable archive exists.
git --version each time a metadata directory is created.expand gix-testtools fixture support
Note that I did only skim through git.rs,
considering the details of the implementation secondary to the outcome.
gix.rs was refactored quite a bit, helping to provide more utilities
in other plumbing crates to help with this 'gix' avoidance.
Add deterministic repository snapshots covering HEAD, references, reachable
commits, every index stage, conflict-free index trees, and exact worktree
contents. Provide a portable form which omits platform-specific filesystem modes
for stable cross-platform assertions.
Add writable Git-version-aware fixture APIs for copy and execute creation modes.
Require archived fixtures when the selected Git is incompatible, without running
unsupported scripts or post-processing.
Use the Git executable selected by gix-path consistently for version checks,
helper commands, and fixture scripts, including PATH selection for scripts.
Harden signing fixtures with command-compatible paths, isolated homes, and
complete SSH key pairs.
git --version each time a metadata directory is created. (4314d09)gix-attributes (e11d7a2)gix_quote::ansi_c::undo().<csr-id-e55f4ee230ed3164df5145c7a2b212464bb9db99/> allow to ignore IO errors when reading configuration files. Sometimes, IO errors can occour consistently when reading from certain paths (on Windows, really), and it should be possible to not only see which path that is but also to ignore them entirely.
Now IO errors contain the path of the failed configuration file. There is also a new option flag to ignore errors (off by default).
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
5dc1f9f)3016a28)ee36e5b)serial_test no default features) (8f2accd)typos tool. (2321eb9)01277a6)
</details>Make reqwest TLS backend configuration easy. We provide the choice of native-tls or rust-tls. If none is provided, the user can configure on their on
Make reqwest TLS backend configuration easy.
We provide the choice of native-tls or rust-tls. If none is
provided, the user can configure on their on similar to how it's done
in git-repository.
Please note that a choice now has to be made or HTTPS will not be available, so use one of…
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
reqwest TLS backend configuration easy. (3ddbd2d)
</details>A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
29a0870)e06f5f5)
</details>This releases fixes gix fetch so that it is able to clone or fetch pytorch or other repositories on case-insensitive file systems.
This releases fixes gix fetch so that it is able to clone or fetch pytorch or other repositories on case-insensitive file systems.
It's also an attempt to trigger CI to build binary releases.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gitoxide.http.connectTimeout for more control for git clients (2ab80e4)no_proxy environment variable support (f0625de)A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
93e75fe)895e482)0f411e9)
</details>gix remote ref-map --show-unmapped-remote-refs. That way it's more obvious to see what was filtered out by ref-specs.
gix remote ref-map --show-unmapped-remote-refs.
That way it's more obvious to see what was filtered out by ref-specs.
It's also great to validate that server-side filtering via ref-prefix will not send refs that are referred to by symbolic refs that are not filtered out. That should be fine as it's all about objects, it's just something to deal with as we may have to deal with symbolic refs that aren't in the set of refs the server sent to us.
diff algorithm is controlled by git configuration diff.algorithm
ein t hours allows to specify the amount of worker threads.
collect stderr and print it afterwards to avoid intersection with line progress.
Previously it would happen that stderr would be printed directly and mix
with the line progress (as in -v) which also prints to stderr.
Now errors are collected and output at the end once the line renderer was already shutdown.
lock_mode from all methods dealing with reference edits.
It is now read from core.filesRefLockTimeout accordingly.gix remote --url in favor of determining the intention similar to git fetchClippy helped 1 time to make code idiomatic.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix remote ref-map --show-unmapped-remote-refs. (e973dfe)diff.algorithm (30d32e7)stderr and print it afterwards to avoid intersection with line progress. (3a05328)clone and print once entire clone is done (9a476df)gix clone (23a5e8b)core.checkState (8b2aba1)gix progress (0e9bd41)init.defaultBranch - now used by custom initialization. (4d6d7bb)gix fetch (c47dcc6)gix remote --url in favor of determining the intention similar to git fetch (92bbe33)--url for arbitrary urls when fetching (8c7351c)gix fetch (5b72d27)lock_mode from all methods dealing with reference edits. (3a0fb1b)gix progress show (92e082a)ein t hours allows to specify the amount of worker threads. (20259da)index.version for when we can write V4 indices. (da96d34)extension.worktreeConfig (fe1e646)init.templateDir to gix progress (9fab050)diff.algorithm (b1edb9e)git-diff for a 2x speedup when calculating line changes (296f3b6)gix progress records (b05a2e7)clone. variables (8b804a3)A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
ea9fd1d)e6cc618)addd789)94c99c7)56c005b)8ef1cb2)
</details>A maintenance release to restore MSRV (1.64) support.
A maintenance release to restore MSRV (1.64) support.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
compatibility with bstr v1.3, use *.as_bytes() instead of .as_ref(). as_ref() relies on a known target type which isn't always present. However, once
bstr v1.3, use *.as_bytes() instead of .as_ref().
as_ref() relies on a known target type which isn't always present. However, once
there is only one implementation, that's no problem, but when that changes compilation
fails due to ambiguity.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
9604783)bstr v1.3, use *.as_bytes() instead of .as_ref(). (135d317)c56d336)
</details>One column per quarter.