NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
crates.io
crates.io, #1287 most downloaded on crates.io
A crate to handle git references
Latest stable
0.69.1
Last release 1 months ago
22 Oct 2026
Ships on a steady schedule
a new release about every 4 weeks
Nearly every release is documented
notes for 58 of the last 60 stable releases
2 versions withdrawn
withdrawn after publishing
4 years old
64 releases · first in 2023
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Nothing published for this version
add convenient RefEdit constructors While reviewing the the actual API in detail with changes, I merely skimmed the usage of them, also assuming that
<csr-id-f5b3feb54438b4361b77403ea788a606ecd96b40/> add convenient RefEdit constructors
While reviewing the the actual API in detail with changes, I merely skimmed the
usage of them, also assuming that they incorrect usage would cause test failures.
<!-- agent --> Cover standard updates and deletions, configurable reflog handling, prebuilt changes, and symbolic-reference dereferencing.
Adopt the constructors throughout the workspace so callers express intent without repeating common defaults.
<csr-id-87ed136beb5172ec945829aea877e5a26eb1122f/> explain unsupported reftable storage when reading HEAD
<!-- agent -->
gix status reports Git's refs/heads/.invalid placeholder as a
malformed symbolic reference, hiding that reftable is unsupported.
Recognize that exact target in the shared loose-reference decoder so
HEAD lookup reports the unsupported backend. Other invalid symbolic
targets retain their existing validation errors.
Git reference: checkout 1630431f326e15fcde608827b5ff38422528eb59,
refs.c::refs_create_refdir_stubs() and t/t0610-reftable-basics.sh.
Git writes this placeholder in ordinary and linked worktrees, and now
also uses it for alternate reference storage. Mention reftable without
assuming it is the only possible backend. Local Git 2.50.1 resolves
the real fixture's HEAD to refs/heads/main despite the placeholder.
The new decoder regression failed with the original invalid-path error before the fix. A nearby invalid target still reports name validation, and the existing real-reftable repository test now checks the cause.
<csr-id-fb36616cba282af08e1104f33fb52f526a804b30/> replace forwarding errors with metadata and recovery signals <!-- Byron -->
Took a closer look over about 40% of the commit, skimmed/skipped the rest it. So not a complete rubber stamp. Later-on, a lot of these explicit downcasts should be turned into quick classification checks.
<!-- agent -->
Return canonical Exn errors from reference operations and gix::Error at
porcelain boundaries. Preserve native parser, filesystem, lock and custom
name-conversion sources instead of rewrapping them in operation-specific enums.
Use documented Metadata dictionaries for diagnostic paths, reference names,
input bytes and positions. Keep concrete signals for absent references,
malformed loose references, stale expected values, existing references and
missing committer identity. These support GitButler-style recovery without
string matching; stale reference values still require reconciliation before
retrying. Fetch only treats an absent referent as unborn, propagating malformed
referents and read failures.
Remove empty error namespaces and duplicate conversions along with their workspace callers. Preserve unterminated packed input and count peeled lines when reporting iterator positions.
<csr-id-1487c6fc27c6fc1d59e24187eaaedf31431be490/> migrate errors to gix-error <!-- Byron --> rubberstamp
But looked into it more to see why it has so much more code. The simple answer is that it basically doesn't use gix-error,
but writes error types manually.
This needs rework.
<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)fb36616)daf73b5)1487c6f)4b9ff51)6b2f33d)HEAD (87ed136)a095334)4b42e0c)RefEdit constructors (f5b3feb)7e35849)888677a)6704303)
</details>Your coding agent can read these notes before it upgrades. Set up the MCP server →
compare names and references with natural counterparts <!-- agent -->
<csr-id-72e8fd1a29c7f4351b659bdd7b0bf5b5a29e3e36/> compare names and references with natural counterparts <!-- agent -->
Allow owned and borrowed reference-name types and namespaces to compare symmetrically with text and byte strings.
Allow raw, loose, and packed references to compare with names, text, and byte strings by projecting their full name, while same-type reference equality remains structural and includes targets and peeled values.
Keep these heterogeneous reference comparisons one-way, with the reference on the left, so references with different structural values cannot form a non-transitive PartialEq chain through their shared name.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
e52fe9d)47536a5)72e8fd1)b8914ff)
</details>terminate lock error parent traversal <!-- agent --> A dereferenced reference update could loop forever while relabeling a leaf lock acquisition error
<csr-id-afc798c55893c58d6d65bf2b24170d484986f400/> terminate lock error parent traversal <!-- agent --> A dereferenced reference update could loop forever while relabeling a leaf lock acquisition error because the traversal did not advance at its root parent.
Add a regression that locks the referent of symbolic HEAD and expects the lock error to return under HEAD. Advance the cursor on every parent so nested symbolic chains terminate and retain the initiating reference name.
<csr-id-1452553115e0b23a43c3ef7f31984f049f0b2e2f/> use gix_testtools::object_hash in a few tests
<csr-id-89468ae83343150a93509ab5127f31910f750193/> assert that transactions hold a constant number of file descriptors
lock_ref_and_apply_change() writes each lock's content and closes it right
away, retaining only a gix_lock::Marker, so preparing a transaction needs
O(1) open files rather than one per edit. Nothing guarded that property, yet
losing it is invisible in small transactions and fatal in large ones: a fetch
updating thousands of refs would die with EMFILE at the ~1000th lock under
the default ulimit -n 1024.
The test prepares and commits 300 edits with RLIMIT_NOFILE lowered to 96.
As that limit is process-wide and sibling tests share the process under plain
cargo test, where they could hit EMFILE spuriously, the test re-executes
itself as a child process marked by an environment variable, and only the
disposable child lowers the limit. The parent asserts the child reports
"1 passed", so a name that stops matching cannot pass silently as 0 tests run.
Verified to fail when each prepared edit leaks a single descriptor.
<csr-id-30f0d73b96871f37e1bc9a511522f51f99fba2fa/> remove object_hash from Options
gix_ref::file::Store::at into at and at_opts.gix_ref::file::Store::for_linked_worktree as well.gix_ref::Store::at as well.This forces callers to explicitly choose a hash, eliminating the risk
that Sha1 is implicitly chosen for them in SHA-1/SHA-256 builds
through Default::default() without them being aware of it or noticing.
This comes at the cost of callers having to always pass the hash, but
that seems like a reasonable trade-off.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
afc798c)ebe9095)f3bbfad)gix-testtools (0cbe539)5cc9287)e5452ba)1f311a1)object_hash from Options (30f0d73)2e929a3)gix_testtools::object_hash in a few tests (1452553)2a4d996)Store::at() where possible (17fea2a)cc3ee80)ab4fcb0)86ae4e0)1eced45)89468ae)ae8845a)
</details>remove global lock optimization to align with Git Previously, a transaction would rely on the packed-refs lock only when available, and skip per-ref l
<csr-id-cde8272517fe1480ad283fbbbe1cea0d488e75e9/> remove global lock optimization to align with Git Previously, a transaction would rely on the packed-refs lock only when available, and skip per-ref locks entirely.
This would, however, incorrectly serialise ref writers globally, giving it the same write performance as ref-tables, while allowing races with Git processes.
<csr-id-4aae42578517c5d1bfd4981e79d4956ea650351b/> check Windows device names before acquiring lock Move the prohibit_windows_device_names validation ahead of lock acquisition in lock_ref_and_apply_change(). Previously the check ran inside ref_contents(), which is called by read_existing_ref() after the .lock file was already created. For a ref such as refs/heads/CON the lock path CON.lock is itself a reserved Windows device name, so prepare() would fail during lock acquisition (or open the device) rather than returning the configured validation error.
Extract the device-name check from ref_contents() into a new check_windows_device_name() helper on the store and call it at the top of lock_ref_and_apply_change(), before either the Delete or Update branch tries to acquire a lock. ref_contents() still delegates to the same helper for callers that read refs outside the transaction path.
<csr-id-8480e2aea4e713c277bfb0a05ff701e1d42302be/> close TOCTOU race in CAS check during ref transaction prepare Read the existing ref value after acquiring the lock rather than before, so the PreviousValue check compares against a value that cannot be changed concurrently. Without this, two transactions can both read the old value, serialize through the lock, and both pass the CAS check — silently losing one update.
The TOCTOU fix moved the existing-ref read under the lock, which for the
Change::Update branch is now after lock acquisition. A path-prefix
collision (creating a/b while a is a ref file) therefore surfaced via
the lock's create_dir_all as AlreadyExists, reported as the misleading
LockAcquire(PermanentlyLocked) rather than the historical
Io(NotADirectory).
Thanks to the gix-fs fix, lock-acquisition I/O errors surface as Error::Io
(reserving Error::LockAcquire for actual contention), which restores the
historical Io(NotADirectory) for path-prefix collisions in the
Change::Update branch.
<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>
842bc44)cb6ec7d)f0ec710)c16b5a1)43ff87a)cf3053a)27aec47)e9c973d)d533f0c)7471d07)cde8272)43dd683)7a1ebfb)4aae425)8480e2a)d785bbc)mmap2 to avoid potential for unsoundness (eda41b1)1b1541e)
</details>tolerate NUL suffixes in symbolic ref files Loose symbolic ref files can contain bytes after a NUL terminator. Git treats those bytes as invisible whe
<csr-id-5d702e36b7489bd2fdc3529688aca480c5f29ac0/> tolerate NUL suffixes in symbolic ref files Loose symbolic ref files can contain bytes after a NUL terminator. Git treats those bytes as invisible when reading the referent, so a HEAD file like 'ref: refs/heads/main\0...' still resolves to refs/heads/main.
gitoxide read the entire line until CR/LF before validating the symbolic target, which made the embedded NUL fail refname validation.
Match Git by stopping symbolic target parsing at the first NUL byte, while leaving direct object ref parsing unchanged.
Git baseline: local Git checkout 7760f83b59, refs/files-backend.c parse_loose_ref_contents() uses C-string semantics for symbolic referents; 'git symbolic-ref HEAD' returns refs/heads/main for a HEAD containing 'ref: refs/heads/main\0codex-hidden-head-metadata: status-clean-demo'.
<csr-id-c3ee5991fe9cbe0d9b229f1cc0b1b05d55a30f1c/> skip name validation in packed-refs binary search to unlock performance
<csr-id-9f432ef509daf09dc1a5bb3cd8201bef81d881ed/> handle loose ref path-prefix collisions
The GitButler branch creation flow reported that
repo.try_find_reference("refs/heads/A/new") could fail with a low-level
NotADirectory error when refs/heads/A already exists as a loose ref. That
lookup is asking whether the longer ref exists; the path-prefix collision
matters to creation/update code, but find should report absence for that
candidate.
Git reference: refs/refs-internal.h documents ENOTDIR as the case where a
ref prefix is not a directory, alongside ENOENT for non-existing refs. For
lookup, both mean the requested ref candidate was not found.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
6428edc)1514b0f)5d702e3)66f70f3)a8b885d)c3ee599)4f089fc)c9191ab)9f432ef)f7d4f33)
</details>retry the current commit when graph parents are corrupt
retry the current commit when graph parents are corrupt
Both Simple traversal paths pop the current commit before decoding its
cached parents. If parent iteration fails, dropping the cache and recursively
requesting the next commit skips the popped commit and its entire ancestry.
With an out-of-range inline parent, a two-commit gix revision walk could
therefore succeed with an empty result.
Put the current commit back at the front of the topology queue or into the
date queue with its existing priority, then continue the loop after disabling
the cache. The object database retries that same commit without recursion;
any object lookup or decoding failure is still propagated.
The regression corrupts a disposable graph, confirms that Git rejects it,
and checks that the existing gix fallback policy preserves both commits
across breadth-first traversal, both date orders, cutoff sorting, and
first-parent traversal.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
10c58bb)575113d)gix-testtools (ce9e6bd)4743361)1980190)e3d5a04)ab2fee1)2cb17b2)e10d5f6)3675a8d)3af9b4a)d3e4c17)23af41a)gix_object::Data (4309fa4)gix-testtoolsand rename hash_kind -> object_hash (d9648e8)adb8328)
</details>5 commits contributed to the release over the course of 13 calendar days.
Category::is_remote_tracking_branch().
Mere convenience.Look at https://github.com/GitoxideLabs/gitoxide/issues/2491 and compare this with what Git at /Users/b yron/dev/github.com/git/git does. I think it will allow newlines and just trim whitespace. Once validat ed, create a test in
gix-refto reproduce the issue, then fix it.
sha-256 support to gix-ref.
This predominantly restricts parsing so it won't allow any hash
but the one that was passed.<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>
1bf4099)53f880c)Category::is_remote_tracking_branch(). (d5f9bf5)87b2da8)sha-256 support to gix-ref. (731248f)gix_hash::Kind (d4439cd)winnow and replace it with hand-implemented parsers everywhere. (91c854e)4d5ba23)2c3a08e)
</details>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)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.
migrate errors to gix-error
rubberstamp
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.
Category::to_full_name() to be able to produce any full name.
Previously it learned to reject certain invalid branch names, but this has to
be done separately and led to some unpleasant changes in gix as well.refs/heads/HEAD just like Git in Category::to_full_name()
See https://github.com/git/git/blob/cf2139f8e1680b076e115bc0b349e369b4b0ecc4/refs.c#L776-L778
for the source of this rule.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
f9fbcba)63b8419)0396152)7d50c30)gix-object (6df1d55)444a92b)package.include patterns more specific so they don't match ignored files (c2c917f)e51c40b)Category::to_full_name() to be able to produce any full name. (5b229c6)420c5df)6a5a0ec)refs/heads/HEAD just like Git in Category::to_full_name() (4b4fba2)44020e0)9d04035)98bae84)
</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>
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)f7277f3)
</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-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
ecf90fc)228caf7)GIX_TEST_FIXTURE_HASH for gix-commitgraph and gix-pack. (d51b858)9327b73)
</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-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
d66ac10)5c9e6ae)gix-testtools (fb60c8a)8bceefb)7ce3c55)f7d0975)
</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>
cbbdef5)562e684)fa85ed3)64fb9de)dfeefe2)gix-ref (931c69b)6cff657)gix-commitgraph (1f58905)0a333e5)c663b3f)7be8f90)d914d95)4edc5dd)211b4fb)
</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>
115e208)d6c5b9d)
</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-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
21fecdf)93dd630)703644c)
</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
Category::to_full_name() can now be passed a full name without prefix duplication.
This is for convenience, as it can then be passed a valid partial name.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
82ff92f)bc62b1e)Category::to_full_name() can now be passed a full name without prefix duplication. (d2cd2ef)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>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>Reference::peel_to_id_in_place_packed
Also, update documentation where it was still referring to deprecated
in_place methods to refer to the new methods instead.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
89fb308)4da2927)b188a7d)6cc8464)9365cc3)838ff95)0a576b9)e670294)b813339)442f800)Reference::peel_to_id_in_place_packed (0380496)42f8db5)e179f82)a78bf84)e25ccbf)d8fbe1e)df91659)dc7343c)
</details>This release adjusts writes to lose ref files so they will contain newlines after the hash for compliance with Git.
This release adjusts writes to lose ref files so they will contain newlines after the hash for compliance with Git.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
79ba9d0)gix-ref release (5315180)edcfdc2)6c0cc71)04a18f3)202bc6d)d64f257)473fe52)428412c)8892cb1)std::io::Error::other support. (88dc1c2)784c046)
</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.
Category::to_full_name() to easily generate full names from short ones.file::Store::is_empty()<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)60c29a5)43f92b5)fdf5153)a2741da)dd5f0a4)554ce13)249bf9a)Category::to_full_name() to easily generate full names from short ones. (f8b87f1)f8d7c0a)151e3a5)7ae3797)file::Store::is_empty() (c8a63ab)c3f06ae)d2b4c44)800738a)4408166)8d4c4d1)
</details>https://github.com/GitoxideLabs/gitoxide/security/advisories/GHSA-9857-6mw7-fq2m
gix free trust to easily check the assigned trust level of any given path
This is particularly useful on Windows, which makes it easy to probe existing paths
with ownership that might be complex to reproduce otherwise.Clippy helped 1 time to make code idiomatic.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix free trust to easily check the assigned trust level of any given path (ab2016f)gix-config. (344218a)
</details><csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
e104545)5f7f805)631f07a)
</details>Adapt to changes in gix-actor Use the committer date and author date that are now backed by bytes and interpret these bytes into a gix_date::Time on d
<csr-id-b07f907ba2e01849744c72df35dac57b624f2f85/> Adapt to changes in gix-actor
Use the committer date and author date that are now backed by bytes and
interpret these bytes into a gix_date::Time on demand.
<csr-id-38b63c2fc9d407b3c634d8b0c72d4d0c104aa5ad/> make fs::walkdir_sorted_new() sort entries by paths literally
This follows up 7b1b5bf864e74706aefeb1213e8bdb0545d5464a. Since packed-refs
appears to be sorted by full ref name, loose-refs should also be emitted in
that order.
The comparison function is copied from gix::diff::object::tree::EntryRef. Non-utf8 file names are simply mapped to "" on Windows. We could add some fallback, but callers can't handle such file names anyway.
&RelativePath in *::prefixed() methods.
That way there now is a type to capture requirements.<csr-id-f5385595987e0be84fb56827682df013bf54e09c/> prefixed ref iteration now properly deals with slashes.
Previously, refs/heads/foo/bar would be listed when running
repo.references()?.prefixed("refs/heads/b"). The code identified that
the last component was not a directory and started to match it as a
filename prefix for all files in all recursive directories, effectively
matching refs/heads/**/b*.
This commit fixes that bug but also allows to use a trailing / in the
prefix, allowing to filter for refs/heads/foo/ and not get
refs/heads/foo-bar as a result.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
cc5b696)49fa9f3)db0b095)0bf84db)3b1bef7)c3c6504)gix-date and gix-actor (afdf1a5)70097c0)b07f907)46227e6)06bf1e1)fdc06b1)294902e)&RelativePath in *::prefixed() methods. (108a8ca)5823b22)Cargo.toml files in workspace to gix-features bump (6315536)71275d1)f538559)57c9014)b5e9059)68e6b2e)507d682)94faf51)3ca6811)1612c73)fc5faf2)7502b4a)420e730)
</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-id-d1b357ec53b9e2be2483ae130e25401be795f139/>
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
Clippy helped 2 times to make code idiomatic.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
a06c409)b41312b)38dff41)cd96b64)56ba898)7b17da6), just before ) on same line in function calls (66a5ae1)write::Error::IllegalCharacter description (d1b357e)01bd76d)8776a3e)9dcfd15)16a248b)8e96ed3)11ac79c)fdc57e7)3cd3e2a)783c4e6)8df0db2)
</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-id-17835bccb066bbc47cc137e8ec5d9fe7d5665af0/>
<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>
dea106a)7570daa)1f6390c)7ec21bb)rust-version to 1.70 (17835bc)1ca480a)9193b05)d22937f)
</details>3 commits contributed to the release over the course of 1 calendar day.
> in them.
Previously these confused the signature parser, who gladly
took the entire message as part of the email.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
c1ba571)7ea8582)8fd53bc)> in them. (6abee88)743b979)cbdbb8a)e95afc0)4885e53)2010668)e8b3b41)
</details>make sure ordinary capitalized partial names can be found by partial name. For instance, previously, a ref named A could not be found even though refs
A could not be found even though refs/heads/A existed.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
4000197)8ce4912)bc9d994)aeaebec)<= on 32-bit for some size assertions (fc13fc3)7a40648)0f0e4fe)3fb989b)1fbb946)db5c9cf)
</details>remove workspace lints from Cargo manifests of fuzz-projects. They are not part of the parent workspace.
<csr-id-65f69f72a8a08b3b2462362ec10d1748be48019b/> <csr-id-64ff0a77062d35add1a2dd422bb61075647d1a36/>
<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)795962b)65f69f7)64ff0a7)37c1e4c)af03832)72daa46)cdac4a9)7c2af44)694ebad)c2bdda4)b12c7c9)93e86f1)012a754)649f588)beba720)37ba461)2e0ce50)f992fb7)ec69c88)46cd1ae)1757377)
</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>
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>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>serde support for varous reference name types.ReferenceExt::follow_to_object_in_place().
The missing link that makes it possible to follow to the first object
and then peel the object according to any preferred algorithm.<csr-id-43d8096dcdd797fd015c177cefeb8ee1f0ae5881/> improve naming and change Target::Peeled to Target::Object.
This also renames TargetRef::Peeled to TargetRef::Object to make clear
that it's not necessarily the peeled object that is contained.
Previously these terms were confusing due to the incorrect usage of the
word peeled.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
f2b522d)a65a17f)d19af16)0f25841)242fedc)ReferenceExt::follow_to_object_in_place(). (16b5e7e)Target::Peeled to Target::Object. (43d8096)d51f330)gix-validate (b9cf0f4)7dff447)serde support for varous reference name types. (70d835b)2e00b5e)winnow a workspace dependency (78a7e32)5871fb1)9fd1090)
</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><csr-id-ec1d6b44d7f65ded8ea34914350e723275121776/>
PartialNameCow<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
6232824)a1b73a6)0470df3)99c00cc)15f1cf7)f87322e)gix-testtools (f5a9884)bf3d82a)1e79c5c)ab02aa9)ec1d6b4)8d89b86)c1d7c02)1dfa90d)tar files (dcab79a)9fa1054)2f9f0ac)PartialNameCow (86e50ee)ca31249)9c65d98)ea12fc2)68cbea8)2cefe77)8da55a3)
</details>LineRef is now Copy and remove non-exhaustive After all, this struct refers to what's in a reflog line, which is stable.
LineRef is now Copy and remove non-exhaustive
After all, this struct refers to what's in a reflog line, which is stable.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
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::Store::force_refresh_packed_buffer() to public API
That way it's possible to explicitly refresh if the caller knows that some other
operation might have invalidated the in-memory cache. The mtime based approach
doesn't work reliably on all filesystems due to coarse granularity of time.<csr-id-9555efe8964d3de3c692f79cef390916e34daefb/> assure that special device names on Windows aren't allowed. Otherwise it's possible to read or write to devices when interacting with references of the 'right' name.
This behaviour can be controlled with the new prohibit_windows_device_names flag,
which is adjustable on the Store instance as field, and which now has to be
passed during instantiation as part of the new store::init::Options struct.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
file::Store::force_refresh_packed_buffer() to public API (f2d8955)4f98e94)9511416)d6cd449)6f55f2a)79dce79)1242151)9555efe)d3588ca)048e43e)cargo check (4faf10e)e33efa2)68fd5b3)
</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>
MAP_PRIVATE
That way, the mmap process should work under more circumstances.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
MAP_PRIVATE (88061a1)b050327)52c3bbd)3e5c974)f8ce3d0)9e9b9fe)
</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)A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
45b4470)f2e111f)a663e9f)e175b20)516e105)face359)ae86a6a)7b44c7f)8430442)69cb78b)9470554)b8cba96)
</details>Nothing published for this version
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>precompose_unicode, which is now an extra argument in the Store constructor.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
eb6aa8f)6a2e0be)5d176fc)69c8232)precompose_unicode, which is now an extra argument in the Store constructor. (7523e5c)b6c04c8)
</details>preserve SCP parsing alongside virtual drive prefixes
preserve SCP parsing alongside virtual drive prefixes
The Windows test-fast and fixture suites classified [::1]:repo and
[:[@]:... as local paths because their leading [: matched the broad
virtual-drive check. They also stopped rejecting an empty helper name in
::bar.
Require the drive prefix to end at the URL parser's selected colon. This
preserves the existing bracket-aware SCP interpretation and empty-helper
rejection while retaining digit and Unicode virtual-drive support.
<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)
</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)<csr-id-aea89c3ad52f1a800abb620e9a4701bdf904ff7d/>
packed::Buffer::from_bytes().
This way the source of the packed-refs file contents can be arbitrary.<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)0f71709)d83b4e0)8ee1194)5828f37)fb28daa)packed::Buffer::from_bytes(). (ff18e0b)3be3b15)3e37a22)1691ba6)
</details>add file::Store::set_packed_buffer_mmap_threshold(). That way it's possible to control under which circumstances, if at all, memory maps will be used.
file::Store::set_packed_buffer_mmap_threshold().
That way it's possible to control under which circumstances, if at all,
memory maps will be used..git/packet-refs on Windows.
The solution entails to not use memory maps on Windows which is certainly fine
on todays systems, even though it's likely to add latency.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
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)Reference::peeled is working.gix-object::Find trait<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)f528ae8)f4c3380)5a0d93e)bb3224c)c8bd660)gix-object::Find trait (dbb6886)gix_object and gix_odb. (24e319e)c0e72fb)b65a80b)c2cf20c)Reference::peeled is working. (266c9fc)
</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>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)995bc84)345712d)
</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>
7891fb1)8a60d5b)
</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)dyn trait where possible.
This reduces compile time due to avoiding duplication.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
8bd0456)375db06)dynification (f658fcc)dyn trait where possible. (072ee32)b7560a2)3be2b1c)363ee77)
</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.
<csr-id-ef54aab9e5521add4154ee8d902d62612a9d8d4a/>
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
30b2761)f23ea88)8f3f358)e0c64fd)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)df226dd)266864f)3f8c91f)12f03db)2fb4a54)f0cbf81)9ed7df0)86ea47f)b3f0418)fee441d)b37a909)ac0e81c)86d7fd1)ee75de1)
</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)A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
4604f83)gix-submodule (f3c4311)b629f8a)gix-validate (a8bc0de)6b4a303)ef8ccd9)
</details>5 commits contributed to the release over the course of 2 calendar days.
<csr-id-5f6cf22cd8eda37c151e67b83cdb36d953ee3793/>
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
231ac1c)db63815)e4d2890)f8b1f55)Change type. (5f6cf22)
</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>
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>
107a64e)16295b5)c4cc5f2)5cb3589)2fc66b5)9064ea3)
</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>A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
68ae3ff)c70e54f)e4dded0)
</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>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>
27e8c18)00f96fb)6fc7497)
</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><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)8d2e6a9)gix-actor (4a80e86)gix-date (d575336)
</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>A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
9a9fa96)8f15cec)67da689)0269eed)420553a)89a8cfe)2578e57)dbf8aa1)2087032)3ef5c90)3eff567)9375cd7)b057500)facaaf6)4f879bf)
</details>symbolic refs are now written with a newline. #(836) This should help some tools to work correctly.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
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>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>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)<root>/HEAD twice due to a logic issue.remotes/HEAD if we are looking for HEAD.
This is because we already looked for that in the previous loop, and HEAD/HEAD makes no sense
as this case is made for things like origin as partial name.<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-id-b645d28f9641c6b4022e1e37ad9fe528922ec747/> remove types that are now available in gix-os
<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>
serde1 cargo feature to serde and use the weak-deps cargo capability. (b83ee36)91134a1)30a1a71)282a1a3)3e93141)remotes/HEAD if we are looking for HEAD. (0c79bdf)6ebd61e)14e64e7)8dbd0a6)cdef398)19338d9)gix-fs crate to consolidate all filesystem utilities (f8cc33c)23ee47f)3d47919)gix-os (b645d28)b574a39)
</details>uncategorized refs should not be per-worktree When creating a new ref from using a Repository instantiated from a linked worktree, if the ref did not
<csr-id-3d6832cb0ea5dc4b3d798fd4ff86602df8d54407/> uncategorized refs should not be per-worktree When creating a new ref from using a Repository instantiated from a linked worktree, if the ref did not fit one of the well-known categories, it would be incorrectly stored as a per-worktree reference instead of a shared reference.
For example, the reference "refs/stacks/linked" does not fit any of the well known categories. According to git-worktree(1), this ref should be shared across all worktrees; i.e. located at $GIT_COMMON_DIR/refs/stacks/linked and not in $GIT_COMMON_DIR/worktrees/linked/refs/stacks/linked.
This change tweaks the control flow so that uncategorized refs correctly fallback to being relative to commondir while still placing refs that are supposed to be per-worktree in the per-worktree location.
<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>
A maintenance release without any user-facing changes.
A maintenance release without any user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
c1f1bfb)c66e298)531dd19)01277a6)
</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>A maintenance release without user-facing changes.
Clone for PartialName.
Also improve documentation for FullName* and PartialName* types.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
29a0870)e06f5f5)Clone for PartialName. (8e8c71b)
</details>One column per quarter.