NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
crates.io
crates.io, #1455 most downloaded on crates.io
A crate of the gitoxide project for implementing git protocols
Latest stable
0.68.0
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 59 stable releases
1 version withdrawn
withdrawn after publishing
4 years old
60 releases · first in 2023
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
9 commits contributed to the release over the course of 13 calendar days.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
794eeef)1d7bac7)80f4b03)d2d078f)95043b9)f819565)1c25831)d9f7c85)5fb3dcf)
</details>Your coding agent can read these notes before it upgrades. Set up the MCP server →
pass HTTP challenges to credential helpers <!-- agent --> Noninteractive credential helpers can need the server's account hint to select a cached iden
<csr-id-5dbaa2e9e6c5e193c8b3edb29ad1f716194a85db/> pass HTTP challenges to credential helpers
<!-- agent -->
Noninteractive credential helpers can need the server's account hint to
select a cached identity. Forward AuthenticationRequired challenges from
the transport into the credential callback during the authentication retry.
Errors without this payload continue to supply an empty challenge list.
An isolated end-to-end regression uses a disposable repository, a loopback
HTTP server, and fictitious credentials. With GIT_TERMINAL_PROMPT=0 and
GCM_INTERACTIVE=never, its helper returns credentials only after receiving
the server's hint. The original reported credential-store configuration
remains unconfirmed; the regression exercises the documented wwwauth[]
interface needed for this behavior.
<csr-id-a54128889532dc1c9219403e6a992b45487fe564/> ignore dangling refs during fetch negotiation <!-- agent --> Fetch negotiation peels every local reference to seed its have set. A symbolic reference whose target was deleted therefore aborted the entire fetch before any ref updates, unlike Git.
Skip only the missing-referent peel error while continuing to surface cycles, malformed references, I/O failures, and missing objects. Add a local-transport regression that fetches successfully in the presence of a symbolic reference.
<csr-id-5d71252e4acc161924de66d11b07888b13a142b2/> migrate errors to gix-error <!-- Byron --> rubberstamp
<csr-id-4b42e0ce80ae934cae4f102f44c392581758608f/> raise MSRV to Rust 1.88
<!-- agent -->
The newly published dua-core 3.3 release used by linked-worktree removal
requires Rust 1.88, so raise every workspace crate and the advertised badge
together.
Keep the MSRV checks buildable by selecting the latest sysinfo and rusqlite
release lines that support Rust 1.88.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
5dbaa2e)37860b3)6356013)daf73b5)5d71252)4b9ff51)2fb9b8a)a095334)4b42e0c)7e35849)888677a)e3a6fa1)a541288)dda600d)
</details>4 commits contributed to the release over the course of 1 calendar day.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
3ebca8b)6704303)e52fe9d)47536a5)b8914ff)
</details>6 commits contributed to the release over the course of 30 calendar days.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
0c541c7)d2af4ed)ebe9095)cc3ee80)ab4fcb0)ae8845a)
</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-id-c3f2244541f0b6419d30782fbae825d33bd5fe16/> replace maybe-async with bisync.
Replace the globally feature-selected maybe-async dependency with bisync 0.3 and
re-export the locally selected macro mode from gix-protocol.
Also use it to deduplicate portions which previously couldn't be handled.
<csr-id-582d7b56cc09cdafaa8db2fb34457f6970c39ce7/> adapt to lifetime-free configuration files in gix-config
Update repository configuration storage, snapshots, overrides, and caches
to use the self-contained gix_config::File representation. Configuration
can now move through repository initialization, cloning, and remote setup
without artificial input lifetimes or conversions to 'static.
BString, PathBuf, OsString, and FullName values
from configuration-derived lookups.Option<Result<T, E>> to
Result<Option<T>, E>, allowing errors to propagate naturally with
?.AsBStr in
configuration setters, converters, remote lookup, and remote saving.Cow construction, into_owned(), and redundant
cloning from configuration consumers.Adapt config-tree conversions for the new owned values and optional-result shape, including booleans, integers, paths, URLs, refspecs, timeouts, compression levels, and reference names.
Return owned remote names, default remote names, branch tracking references, and submodule paths so these results are independent of the repository configuration borrow. Protocol feature values likewise use owned strings.
Update repository opening, initialization, cloning, remotes, filters, status, submodules, and related tests to use the lifetime-free APIs.
<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)adf4b7a)2619919)maybe-async with bisync. (c3f2244)c16b5a1)43ff87a)55b5158)gix-config (376e946)gix-config (582d7b5)cf3053a)27aec47)e9c973d)d533f0c)1b1541e)
</details>5 commits contributed to the release over the course of 13 calendar days.
<csr-id-6a7e5f432f00481dd2260161a83b5b41d4978fed/> echo object-format in all v2 commands A v2 client must report its object format to the server, otherwise the server assumes SHA-1 and aborts the request with a "mismatched object format" error when talking to a SHA-256 repository.
This affects both ls-refs and fetch. A persistent connection retains the object format negotiated during ls-refs, but a stateless transport like HTTP sends each command as its own request, so every v2 command must echo the object-format the server advertised.
So add the echo to Command::default_features so it applies to every v2
command and permit object-format during v2 feature validation.
Also add v2 wire-format sha256 tests for ls-refs and ref-in-want.
<csr-id-96bf6982a8c3f459a10b96314643c50603f6e8f0/> accept sha256 object-format from servers
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
6428edc)d86b01d)048d4a5)da6b267)ed998d1)6a7e5f4)96bf698)155ff6d)9402adc)f7d4f33)
</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.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
10c58bb)278d7ec)sha1 and sha256 forwardings for all crates (09b982c)ab2fee1)2cb17b2)e10d5f6)3675a8d)adb8328)
</details>Headline benefits of this extra-curricular release are various security improvements, and greatly improved error handling and consisstency. Plumbing c
Headline benefits of this extra-curricular release are various security improvements,
and greatly improved error handling and consisstency. Plumbing crates for instance will now
use a standard std::error::Error compatible error type.
Besides that, the tracing of all commands was greatly improved.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
<csr-id-91c854e7b9f41738d0fde825cd474b8c00c1a49b/> remove winnow and replace it with hand-implemented parsers everywhere.
This will allow for simplified maintenance and editing (both human and machine)
down the road, and enable additional performance optimisations.
Parser compbinators to me ultimately were a failed experiment as I couldn't maintain them anyway, with it being too difficult for me to grasp and express everything in its very own kind of language, with a lot of different things to consider.
Note that this also removes detailed errors from all parsers that previously
used winnow, with the option to re-add those if there is demand.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
53f880c)winnow and replace it with hand-implemented parsers everywhere. (91c854e)4d5ba23)
</details>Headline benefits of this extra-curricular release are various security improvements, and greatly improved error handling and consisstency. Plumbing c
Headline benefits of this extra-curricular release are various security improvements,
and greatly improved error handling and consisstency. Plumbing crates for instance will now
use a standard std::error::Error compatible error type.
Besides that, the tracing of all commands was greatly improved.
remove full-screen progress mode <!-- agent --> Full-screen progress required separate command and UI threads plus channel coordination, while line progress already covers long-running commands and works with independently buffered tracing.
Remove --progress, --progress-keep-open, and the prodash-render-tui feature. Keep synchronous line progress as the only progress UI.
make trace output independently configurable <!-- Byron -->
Quick review only, as it's mostly about tracing and gix which both aren't super
important, and are seemingly working well. An extra agent-review couldn't
find anything either.
<!-- agent -->
Replace the old boolean trace switch with a bounded -t/--trace counter:
forest INFO and DEBUG at one or two occurrences, then flat DEBUG and TRACE at
three or four. Keep --threads long-only and route tracing independently of
verbose and progress rendering, including commands with bespoke execution paths
and corpus runs.
Initialize display tracing once before repository discovery, buffer it outside
prodash, and emit it after command and progress teardown. Format forest and
flat output with ANSI, then adapt the final stderr write so terminals get color
while pipes and NO_COLOR remain plain.
Corpus worker subscribers share that sink while retaining their complete
JSON trace storage, and flat modes include completed spans. gix tix remains
delegated to Tix so it installs only one subscriber.
add and remove linked worktrees from the CLI <!-- Byron -->
rubber-stamp mostly for gitoxide-core changes, did look at it though just to be sure.
Journey test was present but removed.
<!-- agent -->
The CLI previously exposed only worktree listing, despite gix supporting
both checkout and safe removal. Add worktree add (alias create) and
worktree remove using those APIs.
Creation follows Git's local-branch and detached-revision selection, including
destination-basename defaults and -b. It retains new branches after setup
failures, uses the existing listing format on success, and reports incomplete
checkouts. Removal maps repeated -f flags to dirty-worktree and lock overrides
while retaining branches.
Both commands use the existing repository, configuration, and progress options. Unsupported JSON output is rejected before mutation.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
AsHashKind (106db87)gix free index (a8e3143)<csr-id-c86b00b50fa756cce4e117878a6e10de489674d3/> Introduce RefPrefixes type
The RefPrefixes type captures the intent of building a set of
ref-prefix arguments for the ls-refs protocol.
Since refspecs are the natural type that these are built from, as seen
in handshake/mod.rs, a constructor is provided in the form of
RefPrefixes::from_refspecs.
For other, external API users RefSpecs::new and RefSpecs::extend
are provided.
This is also a breaking change to LsRefsCommand::new() which now takes
Option<RefPrefixes> as first parameter.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
f9fbcba)444a92b)package.include patterns more specific so they don't match ignored files (c2c917f)44020e0)9d04035)700ad9e) ([df41a64`](https://github.com/GitoxideLabs/gitoxide/commit/df41a64851de31b5b5581b39efe18af4e5becfbc))82674cb)c86b00b)98bae84)
</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>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>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.
nonempty in gix-protocol<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
ecf90fc)29040a8)nonempty in gix-protocol (78b0a6f)9327b73)
</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>
d66ac10)8bceefb)7ce3c55)f7d0975)
</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)std::ops::ControlFlow where possible<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
cbbdef5)562e684)std::ops::ControlFlow where possible (5c1bd03)0a333e5)c663b3f)7be8f90)9e1ba5e)3bc0c47)211b4fb)
</details>Strange - automatic release notes weren't generated or didn't arrive here. Have to look into that. Meantime, let's use the GitHub generated notes.
Strange - automatic release notes weren't generated or didn't arrive here. Have to look into that. Meantime, let's use the GitHub generated notes.
fuzzed_timeout on windows-11-arm by @EliahKagan in https://github.com/GitoxideLabs/gitoxide/pull/2619gix-pack by @cruessler in https://github.com/GitoxideLabs/gitoxide/pull/2602GIX_TEST_FIXTURE_HASH for gix-index tests by @cruessler in https://github.com/GitoxideLabs/gitoxide/pull/2598should_interrupt per entry in index_as_worktree by @sharifhsn in https://github.com/GitoxideLabs/gitoxide/pull/2631Full Changelog: https://github.com/GitoxideLabs/gitoxide/compare/v0.54.0...v0.55.0
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
115e208)d6c5b9d)
</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><csr-id-37a42bde69d1a80080f91a78514565508b278876/> <csr-id-0f58b0184b34df3b4e530ce4f7ab26369f882f99/> <csr-id-e5498415a704859fe8385b09e46539372df04d9f/> <csr-id-7e08219644fb84550b82e4c36cdec2d08a06136d/> <csr-id-ab3cce472efc4f6469d99a0d3a425d58ac2140b9/> <csr-id-c26efb9e733cb33a38ef885eded915e17e61bd9c/> <csr-id-0021f9daec773f381c6f10bd310cd0f8c5077d54/> <csr-id-7a60e7846a0e077a1c7f6d560461ee81ae0d4e85/> <csr-id-3b4e06ac9f6b600f58c459a034e6cfaac7221514/> <csr-id-3bc580173ca8f6e95f0e8996a05a451dc199dfa3/> <csr-id-c6d76885bdddc2d6a230618b8ba3f4ebae715987/> <csr-id-149bcfca6a35ebfd7493ee8517905a6b6ca58dd5/>
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
21fecdf)eab774c)9d936fb)ab3cce4)c26efb9)0021f9d)7a60e78)37a42bd)0f58b01)3b4e06a)3bc5801)e549841)c6d7688)149bcfc)93dd630)703644c)7e08219)
</details>This release was made to supersede the borked gix v0.82 release, as it released gix-actor as patch-update which broke v0.81 and probably earlier versi
This release was made to supersede the borked gix v0.82 release, as it released gix-actor as patch-update which broke v0.81 and probably earlier versions as well.
<csr-id-4c40484391c32b4d42b5904a1a0c42639369673e/> <csr-id-36c2be80e61a7a0ef637a5385e1960de13261984/> <csr-id-541a7a6aab6a56fa2949a5577acbacf6dc59a9dd/> <csr-id-19a005135b91641a19a3a70fd714985ce1203333/> <csr-id-50120de92dab3d8347672df7a43df02291162c9a/> <csr-id-37ab03687a940c89131141b882e5ef1a7fef85be/> <csr-id-f05dfab881481de5de1d23e3266cad9c069f59c5/> <csr-id-b05eba5cca4294b9baeafd0c15885cefd21d0d6c/>
Handshake::ref_map() to produce a ref-map from a V1 or V2 handshake.gix-packeline features additive.
For good measure, everything that was touched is marked as breaking change.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
82ff92f)3c2b422)service parameter back to not hardcode the handshake for fetches. (c9a97db)server parameter. (36c2be8)0ac3080)Handshake::ref_map() to produce a ref-map from a V1 or V2 handshake. (aeee982)handshake::Outcome into Handshake type. (541a7a6)48fdf5d)19a0051)4c40484)50120de)37ab036)f05dfab)b05eba5)102077b)7ce40ef)87d5419)6e89afa)c2050d0)6566ec9)b6d5822)cbf7445)7289a04)bce8468)gix-packeline features additive. (f2c6a19)fbf9c39)
</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-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>Merge pull request #2163 from cruessler/deprecate-in-place-methods (`42f8db5`)
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
49f8d53)89fb308)4da2927)b188a7d)6cc8464)9365cc3)838ff95)42f8db5)gix-ref (44922d0)dc7343c)79ba9d0)651f9fa)4289ae6)202bc6d)d64f257)589d63e)007e3f6)473fe52)428412c)784c046)
</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
A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
Clippy helped 1 time to make code idiomatic.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
5a919c4)65037b5)c2eb0c1)bfb1c34)f8d7c0a)151e3a5)c3f06ae)d2b4c44)28935a5)dbf65c9)8d4c4d1)
</details>3 commits contributed to the release over the course of 16 calendar days.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
e104545)5f7f805)631f07a)
</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>futures-lite instead of dep:futures-lite in gix-packetline and
gix-protocol.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
cc5b696)49fa9f3)db0b095)0bf84db)3b1bef7)c3c6504)46227e6)06bf1e1)5823b22)Cargo.toml files in workspace to gix-features bump (6315536)b5e9059)68e6b2e)1612c73)fc5faf2)19f50d0)11bd59f)420e730)
</details>Resolve Winnow deprecations (`3cd3e2a`)
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>
d248e3d)ada5a94)b41312b)38dff41)5cb5337)gix_fs::stack::ToNormalPathComponents everywhere. (1f98edb)16a248b)8e96ed3)11ac79c)fdc57e7)3cd3e2a)783c4e6)8df0db2)
</details>7 commits contributed to the release over the course of 27 calendar days.
<csr-id-17835bccb066bbc47cc137e8ec5d9fe7d5665af0/>
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
dea106a)1f6390c)af8f201)gix-refspec (6d7dd9b)7ec21bb)rust-version to 1.70 (17835bc)d22937f)
</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>
<csr-id-e59fc09f12a1c6b27d878525ff6074ac846aa87e/> move all possible code from gix to gix-protocol.
For now, just move the code down and immediately re-integrate in gix
to be able to use its tests to validate it.
This is a breaking change as some types move and change the layout.
<csr-id-6367c7d0a796aff8ee8778916c1a1ddae68b654d/> Add gix-shallow crate and use it from gix and gix-protocol
That way it's easier to reuse shallow-handling code from plumbing crates.
Note that this is a breaking change as gix-protocol now uses the gix-shallow::Update
type, which doesn't implement a formerly public from_line() method anymore.
Now it is available as fetch::response::shallow_update_from_line().
ref_map from fetch() function.
It's only uses for validation of the ref-maps own state, which
is something that can be separate.fetch() to tests so they are the only ones with delegates.
This is a first step towards creating a multi-step fetch() which can
also be used in the gix crate.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
beb0ea8)c1ba571)7ea8582)ca54b8c)5c21ebc)a5f0d29)a542775)ref_map from fetch() function. (5950926)ddeb97f)gix to gix-protocol. (e59fc09)gix-shallow crate and use it from gix and gix-protocol (6367c7d)fetch() to tests so they are the only ones with delegates. (212ea9e)d7b1cce)e8b3b41)
</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>
4000197)8ce4912)bc9d994)700cfa5)gix-packetline-blocking copy auto-generated (325588e)7a40648)0f0e4fe)db5c9cf)
</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><csr-id-64ff0a77062d35add1a2dd422bb61075647d1a36/>
<csr-id-24da857dbd236ae1cc75a4efd0816e717b885c7f/> make V1 shallow announcements possible
<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>
24da857)f1364dc)3f7e8ee)795962b)64ff0a7)37c1e4c)af03832)612896d)6c82f31)649f588)beba720)37ba461)fc45c93)2e0ce50)f992fb7)ec69c88)46cd1ae)1757377)
</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>
4fe330e)f2b522d)a65a17f)d19af16)0f25841)2e00b5e)winnow a workspace dependency (78a7e32)5871fb1)9fd1090)f6a4eb9)
</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>
6232824)a1b73a6)0470df3)99c00cc)c1d7c02)9fa1054)
</details>3 commits contributed to the release over the course of 1 calendar day.
A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
4f98e94)9511416)d3588ca)
</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>A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
095c673)5755271)
</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>
b050327)52c3bbd)3e5c974)f8ce3d0)
</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>
45b4470)f2e111f)5fc379d)c5c69bd)f26f298)a663e9f)e175b20)516e105)69cb78b)9470554)
</details>This is a bit empty as release notes got lost in a series of accidents, but it looks like it wouldn't have been too informative anyway.
This is a bit empty as release notes got lost in a series of accidents, but it looks like it wouldn't have been too informative anyway.
A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
eb6aa8f)6a2e0be)b6c04c8)
</details>3 commits contributed to the release.
<csr-id-3bd09ef120945a9669321ea856db4079a5dab930/>
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
972241f)8c492d7)rust-version manifest field back to 1.65. (3bd09ef)
</details>Add missing command docs + small style fixups Changes that affect the help/usage text shown at runtime:
<csr-id-f952c101cc8686e685074e8604e0f332c06d6767/> Add missing command docs + small style fixups Changes that affect the help/usage text shown at runtime:
Add descriptions for a few gix commands that didn't have it:
gix is-clean, gix is-changed, and gix env.
Add a description of the debug-only ein panic command.
Small spacing and capitalization improvements for consistency.
Add a line break in a /// block for brevity of the top line.
Changes to code style that do not affect what is shown at runtime:
Add . at the end of some /// first lines. (This doesn't
affect runtime behavior because clap normalizes this away.)
Put /// above all #[...] in a few places where it wasn't.
Adjust comment wrapping in a couple of places for clarity.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
<csr-id-f952c101cc8686e685074e8604e0f332c06d6767/>
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
<csr-id-aea89c3ad52f1a800abb620e9a4701bdf904ff7d/>
<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)1691ba6)98b08f4)ff1542c)prodash to latest version (97f62cb)
</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)<csr-id-6295dec2bdd6c3bb35e45db7a486651ebfe50369/> V1 negotiation won't hang anymore The logic previously tried to estimate when a pack can be expected, and when a NAK is the end of a block, or the beginning of a pack.
This can be known because a pack (with our settings) needs two things:
done sent by the client<csr-id-c3edef1c0c49accbb037bdf086dade3ed0e5e507/> make it possible to trace incoming and outgoing packetlines. Due to the way this is (and has to be) setup, unfortunately one has to integrate that with two crates, instead of just one.
This changes touches multiple crates, most of which receive a single boolean as last argument to indicate whether the tracing should happen in the first place.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
6295dec)d3fd11e)55d386a)d3dcbe5)d2ba97c)88f8b34)winnow 0.5.24 (abcfb65)51c7abc)5a0d93e)bb3224c)c0e72fb)b65a80b)eb23338)e7de4c7)c3edef1)
</details>bump gix-transport version to prevent it from being picked up. gix-transport v0.37.1 could accidentally be picked up by older, incompatible, gix versi
<csr-id-8011c73ee401bfca03811a249c46a4dd468af1b8/> bump gix-transport version to prevent it from being picked up.
gix-transport v0.37.1 could accidentally be picked up by older, incompatible,
gix versions which now fail to build.
Thus v0.37.1 is now yanked and replaced with v0.38.0 along with a new
release of gix to go with it.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
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>A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
14ddbd4)68e5432)1347a54)
</details>add first 'debug' version of gix log It's primarily meant to better understand gix blame.
gix log
It's primarily meant to better understand gix blame.--tree-favor to gix merge tree|commit.
With it one can decide which side to favor in case of
irreconcilable tree-conflicts.gix merge file now uses THEIRS instead of OURS where needed<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix merge file now uses THEIRS instead of OURS where needed (0727b56)gix log (c7e04e9)gix-diff (960773e)--tree-favor to gix merge tree|commit. (471e046)A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
7891fb1)8a60d5b)
</details>3 commits contributed to the release over the course of 14 calendar days.
gix merge commit --debug
This yields additional debugging information with details about detected conflicts.gix merge commitsgix merge tree to merge trees similarly to git merge-tree.<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix merge commit --debug (0a5993f)gix merge commits (4a5afc7)gix (8d590f3)gix merge tree to merge trees similarly to git merge-tree. (84707c2)add Url::path_query_fragment()
Expose the decoded path, query pairs, and fragment of Git remote URLs
separately. Consumers can identify repository paths and inspect HTTP(S)
parameters without implementing scheme-specific splitting and decoding.
Recognize delimiters before decoding and reuse validated original spelling
to borrow decoded bytes. Preserve encoded separators, nested escapes,
ordered duplicate query keys, and literal percent text after construction
or mutation. Query pairs use form decoding (+ becomes space); SSH/SCP
paths, existing accessors, and serialization keep their behavior.
Reference Git's connect.c::parse_connect_url() and url.c at
1630431f326e. Use fetch-pack --diag-url to check SSH delimiters;
standalone url-parse does not model that transport.
migrate errors to gix-error
raise MSRV to Rust 1.88
The newly published dua-core 3.3 release used by linked-worktree removal
requires Rust 1.88, so raise every workspace crate and the advertised badge
together.
Keep the MSRV checks buildable by selecting the latest sysinfo and rusqlite
release lines that support Rust 1.88.
Url::path_query_fragment() (cd90fe1)<csr-id-ed327f6163f54756e58c20f86a563a97efb256ca/>
prodash::Count to indicate that nothing more than counting is performed, in place of prodash::Progressdyn 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>
1ff3064)8bd0456)375db06)dynification (f658fcc)dyn trait where possible. (072ee32)prodash::Count to indicate that nothing more than counting is performed, in place of prodash::Progress (24dd870)16cac47)444f970)237657e)8c80dba)b213889)659ebe9)8609aec)b46fe9c)0e8edef)prodash (ed327f6)b7560a2)3be2b1c)363ee77)
</details>support for listing worktrees with gix worktree list
support for listing worktrees with gix worktree list
add first 'debug' version of gix diff tree.
It's primarily meant to better understand gix blame.
add new gix cat command.
It only prints things without fuzz.
Inspired by https://youtu.be/JYH5ILv5g1g?si=bHLBPFJiZyRUTl6u&t=211.
add gix merge-file with similar features as git merge-file
gix merge-base for the CLI
For now it only supports the standard merge-base, but more derivatives
can be added easily on demand.
gix clean warning and help for worktree fixgit clean options
-r/--repositories and --skip-hidden-repositories to make it
clearer what their relationship is, avoid creating the false
impression that repositories are never deleted in the absence of
-r/--repositories, and note that --skip-hidden-repositories
is sometimes needed to preserve not only separate repositories but
the (probably rarer) case of hidden nested worktrees of the current
repository.time to jiff
This swaps out time for jiff. It doesn't completely remove time
from the dependency tree. The last remaining use of time is in
prodash, outside of the gitoxide project.<csr-id-786bfec7c2cf25a68705b6ef09ba6390600742b8/> Unify style in config support info
This builds on b31d6b7 (#1531) by adjusting the capitalization and
quoting style of string arguments in progress.rs that help
document the status of what configuration options are and are not
planned.
Since I believe these strings are not usually rendered as Markdown, and most places that code formatting in Markdown would be used were already written with single quotes, this applies that quoting style consistently.
This applies initial capitalization, which was sometimes but not
always done. It does not apply a consistent style for when a
string will end in a ., which seems already to differ
deliberately for reasons of clarity. That can be adjusted later.
A small amount of minor rewording for clarity is also included.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix commit-graph is (49bca2a)gix diff tree. (0c554e0)gix cat command. (9c8bc03)gix merge-file with similar features as git merge-file (3da2da9)gix merge-base for the CLI (7249291)time to jiff (28ac657)gix clean warning and help for worktree fix (6eb4ea6)gix worktree list (c7213bc)
</details><csr-id-229bd4899213f749a7cc124aa2b82a1368fba40f/>
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
6c62e74)30b2761)f23ea88)229bd48)4604f83)
</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.
fetch::Arguments::add_feature() for unconditional additions of arguments that are supposed to be features.
This differentiation is important to support V1 and V2 correctly, which have a different notion of features with V1
special-casing them, and V2 just sees everything as arguments.handshake::Ref::Symbolic now has a tag field.
This allows symbolic refs to be parsed which are in fact pointing
to an annotated tag as in-between object.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
231ac1c)db63815)e4d2890)f8b1f55)fetch::Arguments::add_feature() for unconditional additions of arguments that are supposed to be features. (d1f9c63)handshake::Ref::Symbolic now has a tag field. (0de7117)
</details>3 commits contributed to the release over the course of 1 calendar day.
A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
0062971)107a64e)16295b5)c4cc5f2)5cb3589)2fc66b5)9064ea3)
</details>This release contains fixes relevant to the safety of checkouts:
This release contains fixes relevant to the safety of checkouts:
checkout respects options for core.protectHFS and core.protectNTFS.
This also adds gitoxide.core.protectWindows as a way to enforce
additional restrictions that are usually only available on Windows.
Note that core.protectNFS is always enabled by default, just like
it is in Git.
more robustness in the face of a trampling-herd of threads loading a single index. The motivating example is here: https://github.com/praetorian-inc/noseyparker/issues/179
Previously, it was possible for a trampling herd of threads to consolidate the disk state. Most of them would be 'needs-init' threads which could notice that the initialization already happened, and just use that.
But a thread might be late for the party and somehow manages to not get any newly loaded index, and thus tries to consolidate with what's on disk again. Then it would again determine no change, and return nothing, causing the caller to abort and not find objects it should find because it wouldn't see the index that it should have seen.
The reason the thread got into this mess is that the 'is-load-ongoing' flagging was racy itself, so it would not wait for ongoing loads and just conclude nothing happened. An extra delay (by yielding) now assures it either seees the loading state and waits for it, sees the newly loaded indices.
Note that this issue can be reproduced with:
'./target/release/gix -r repo-with-one-pack -t10 --trace odb stats --extra-header-lookup'
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
core.protectHFS and core.protectNTFS. (886d6b5)Store::at() where possible (17fea2a)replace fs with gix-fs
gix-fs already provides the filesystem helpers and recursive walkers.
Keeping their duplicate implementation in gix-features adds unnecessary
filesystem dependencies to the foundational feature crate.
Remove the fs module and the walkdir and fs-read-dir features. Migrate
workspace callers to gix_fs, move traversal requests to gix-fs/walkdir,
and update the manifests, lockfile, traversal documentation, and feature
check script together.
fs with gix-fs (cf1ba49)A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
4aca8c2)68ae3ff)c70e54f)e4dded0)
</details>add gix status --ignored support
add gix status --ignored support
add gix status --index-worktree-renames
This enables rename-tracking between worktree and index, something
that Git also doesn't do or doesn't do by default.
It is, however, available in git2.
gix status with submodule and rewrite support.
Submodule changes are now picked up as long as the submodule is
in the index.
Further, it's possible to enable rename-tracking between
index and worktree separately.
add gix is-clean|is-changed
It's a good way to compare the time it takes to run a full status
compared to a quick is-dirty check.
gix submodules list --dirty-suffix for dirty-information
This is a submodule-centric and greatly simplified way of obtaining
describe information with dirty-suffix.
Note that status information is also possible, but it seems
hard to display nicely, which this command isn't great at
in the first place.
add gix commit describe --dirty-suffix
That way a suffix will be added depending on the dirty-state of the repository.
gix status --format to communicate the current format is very simple. (23bea36)gix status --ignored support (84c74ff)gix status --index-worktree-renames (66e87cd)gix status with submodule and rewrite support. (61c002b)gix is-clean|is-changed (98b3680)gix submodules list --dirty-suffix for dirty-information (afd20ca)gix commit describe --dirty-suffix (58231b4)migrate errors to gix-error
raise MSRV to Rust 1.88
The newly published dua-core 3.3 release used by linked-worktree removal
requires Rust 1.88, so raise every workspace crate and the advertised badge
together.
Keep the MSRV checks buildable by selecting the latest sysinfo and rusqlite
release lines that support Rust 1.88.
A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
27e8c18)00f96fb)
</details>add gix clean --patterns-for-entries|-m to help with wildcards.
gix clean --patterns-for-entries|-m to help with wildcards.gix clean<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
-n argument as no-op to make them more compatible. (8959b21)gix clean --patterns-for-entries|-m to help with wildcards. (9863d75)gix clean (e8597f3)<csr-id-bcad5c22049d56a25ef69d6c7a3344e78f9a1d4d/>
SecondsSinceUnixEpoch type where needed.
Previously we used usize which isn't correct on 32 bit systems.<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)SecondsSinceUnixEpoch type where needed. (9f8fa22)
</details>support capabilities^{} syntax to announce caps in empty repos under V1 This is supposed to work for existing code, but doesn't in our case as we real
capabilities^{} syntax to announce caps in empty repos under V1
This is supposed to work for existing code, but doesn't in our case as we really
want to associate a branch. In this case, we can ignore the ref as it's a null
hash anyway.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
2560a2c)298f3d7)capabilities^{} syntax to announce caps in empty repos under V1 (c8e8b9f)
</details>assure we don't stop early on NAK if READY was sent to handle V1 specialty. Seeing READY means a pack will follow, which is exactly the kind of knowle
<csr-id-88670c2ff995e4478f4a40b2733c6c8ca811fa15/> assure we don't stop early on NAK if READY was sent to handle V1 specialty. Seeing READY means a pack will follow, which is exactly the kind of knowledge we want. Thus we now either listen to the client OR to what the server says.
Note that this remedy relies on multi-ack-detailed, which some very old servers might
not support. For those we would be out-of-luck, but that seems acceptable.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
Add rev parse --reference. It's similar to git rev-parse --symbolic-full-name.
rev parse --reference.
It's similar to git rev-parse --symbolic-full-name.mark gix::interrupt::init_handler() as unsafe
The passed interrupt() argument will be called from a signal
handler, so that needs to be documented and the call sites need to
state that they fulfill the contract.
Thanks to @Manishearth for pointing this out.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
rev parse --reference. (193ffcd)gix::interrupt::init_handler() as unsafe (59b8104)
</details><csr-id-877aa2921d8491d301945f86d5a69382e40fb081/> Add fetch::Arguments::is_stateless() to aid proper use of arguments.
When arguments are used, haves are reset every round in stateless protocols, while
everything else is repeated. However, this also means that previously confirmed common
commits aren't repeated unless this is specifically implemented by the user of Arguments.
That caller can now easily determine if negotiations have to be compensated for.
Please note that Arguments explicitly doesn't implement repeating of all prior arguments, which
would also repeat a lot of in-vain haves.
include-tag is now properly handled in V1 fetch arguments
Previously it would be added like it's V2 arguments, which makes using it
in V1 impossible.<csr-id-6a3c02131c9ebca911be5f751e5a6c67fbdbf609/> make V1 stateless negotations work. This is done by working around another V1 negotiation oddity by exploiting client-side knowledge. For very old servers, we probably wouldn't be able to do multi-rounds without dead-locking, but with recent-enough (probably 10 years or so) old git servers all should work fine.
All this to not actually have to implement the V1 strangeness, allowing our code to work smoothly with all permutations of stateless/stateful connections and V1/V2 interactions, with a single high-level implementation essentially.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
9a9fa96)8f15cec)ae845de)6a3c021)include-tag is now properly handled in V1 fetch arguments (c5dc7b4)fetch::Arguments::is_stateless() to aid proper use of arguments. (877aa29)gix-transport (60eaceb)420553a)2578e57)150463c)3ef5c90)9375cd7)facaaf6)
</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>
7ebc9f7)0135158)43ebaf2)
</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-b83ee366a3c65c717beb587ad809268f1c54b8ad/> Rename serde1 cargo feature to serde and use the weak-deps cargo capability.
With it it's possible to not automatically declare all optional dependencies externally visible
features, and thus re-use feature names that oterwise are also a crate name.
Previously I thought that serde1 is for future-proofing and supporting multiple serde versions
at the same time. However, it's most definitely a burden I wouldn't want anyway, so using
serde seems to be the way to go into the future.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
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)d7173b2)e4df557)91134a1)30a1a71)6ebd61e)14e64e7)8dbd0a6)cdef398)19338d9)b574a39)
</details>2 commits contributed to the release over the course of 1 calendar day.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
don't assume that credential providers always return credentials or error during handshake. The type-system allows this even though when getting crede
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
5dc1f9f)3016a28)d4c82e7)
</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 any user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
c1f1bfb)c66e298)3836cc0)cc0f506)gix-packetline (4f45814)531dd19)01277a6)
</details>gix submodule subcommand for simple submodule listing and information retrieval
gix submodule subcommand for simple submodule listing and information retrievalgix index entries --recurse-subomdules to also list submodules.gix index entries with styles and pathspecs.
This adds support for more simple git style, which is faster and thus
allows for more direct comparisons to git ls-files.gix commit verify-signature to do something akin to git ... --show-signature.<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix submodule subcommand for simple submodule listing and information retrieval (1ccbe16)gix index entries --recurse-subomdules to also list submodules. (6bc69e3)gix (ca972a2)Defaults::from_environment() when parsing pathspecs. (2a99034)gix index entries (22477bd)gix index entries with styles and pathspecs. (c30ac0c)gix (a201f0d)gix commit verify-signature to do something akin to git ... --show-signature. (cd6cfe4)gix-archive (feba76d).gitmodule file abstraction (6a2e6a4)
</details>A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
29a0870)e06f5f5)ac34d2e)gix-transport and add V2 test for unshallow fetching (0eecfab)
</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)A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
93e75fe)895e482)0f411e9)
</details>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.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
ea9fd1d)e6cc618)addd789)94c99c7)
</details>compatibility with bstr v1.3, use *.as_bytes() instead of .as_ref(). as_ref() relies on a known target type which isn't always present. However, once
bstr v1.3, use *.as_bytes() instead of .as_ref().
as_ref() relies on a known target type which isn't always present. However, once
there is only one implementation, that's no problem, but when that changes compilation
fails due to ambiguity.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
9604783)bstr v1.3, use *.as_bytes() instead of .as_ref(). (135d317)f872ba8)
</details>fetch::Ref::Symbolic::target is now an option… …to represent the possibility that the server may not be able to strip its namespace if it is not the c
<csr-id-f7f136dbe4f86e7dee1d54835c420ec07c96cd78/>
<csr-id-da68bfb8104ecf58e73e3f99d87f81c90712a2ca/> fetch::Ref::Symbolic::target is now an option… …to represent the possibility that the server may not be able to strip its namespace if it is not the currently set namespace.
Note that the object it points to might still be resolvable and pointing to another namespace.
<csr-id-3d8fa8fef9800b1576beab8a5bc39b821157a5ed/> upgrade edition to 2021 in most crates. MSRV for this is 1.56, and we are now at 1.60 so should be compatible. This isn't more than a patch release as it should break nobody who is adhering to the MSRV, but let's be careful and mark it breaking.
Note that git-features and git-pack are still on edition 2018
as they make use of a workaround to support (safe) mutable access
to non-overlapping entries in a slice which doesn't work anymore
in edition 2021.
<csr-id-02e37f04d7dfeab7067c8273bcd76408cb1f4852/> Support for unborn ls-refs capability if server supports it.
We can also parse it, adding yet another variant to fetch::Refs.
<csr-id-32dc1829a5661f66396d109c8d0a8eaae6b1f532/> use git-credentials in git-protocol
<csr-id-09070a7c17f39383730c3a2b809eec677f79f386/> move fetch::refs(…, protocol, …) to the crate root as ls_refs(…).
This move also removes the protocol parameter as ls-refs is only available
in V2 and the caller is forced to know that after running a
handshake(…) anyway which yields the actual protocol used by the
server.
Note that the client can suggest the version to use when connecting, which is specific to the transport at hand.
<csr-id-35f7b4df164c130fb50fcffcf5de99816c2ca872/> move fetch::Command into the crate root.
This represents much better on how it is actually used, which is for
validation of any Command invoked through the protocol independenty.
<csr-id-a03f8f6cce34618883e8448dd1c31b41c54d9448/> move fetch::agent|indicate_end_of_interaction to crate root
These are generally useful in all interactions, including push.
<csr-id-a3bcf82ae50defa4439862943008647d03d09792/> handshake(…) is now generalized to support git-receive-pack as well.
Note that fetch::handshake() is still present, selecting the correct
service like before, but most of the fetch::Ref parsing is now handled
by handshake::Ref in it's more general location.
There is still fetch::refs(…) which just invokes a V2 ls-refs command
(without that being generalized) as git-receive-pack just supports
V1 at the moment, and making the fetch::LsRefs Command more general
would mean that every command has to be general, at is doesn't matter
anymore if it's used for Fetch or Push.
As long as git won't support V2 for pushes, which it never might, there is no need to introduce this breakage even though it should probably be done before going 1.0.
<csr-id-d05b0b800a553e1e380801fb141e9aa054a6cbd0/> fetch::agent() returns agent string only; fetch() takes agent name as parameter.
<csr-id-aab278f2a3e07edb6d8109e7ffba003b5d5d7857/> don't auto-insert user agent, instead prepare to insert it later.
<csr-id-f957d9a1833af079b01ba6bd6941eb4af6c9e436/> fetch::agent() now returns the agent name, fetch::agent_tuple() returns specific key-value pair.
This is in preparation for allowing user-defined agent strings.
<csr-id-cd867ade55eaec138029c0cf17fa83e0679ef7fc/> fetch::Ref::unpack() returns Option<oid>.
That way the caller has to be aware of the possibility of an unborn
branch (probably the only unborn branch) on the remote.
<csr-id-91f193f73ae37314319f7d055893b95431fd018e/> fetch::Ref::unpack() returns &BStr instead of &BString as ref name.
<csr-id-d2c772e28619f7602ab01285b25e79a7040c9aab/> fetch::Ref::unpack() now returns the peeled object as well.
<csr-id-bab586099a6e21e54932218f7a5c14f8bfc6cabd/> rename fetch::Ref::path to fetch::Ref::full_ref_name.
Previously it was inaccurately named and described due to an
insufficient understanding of the ref database.
<csr-id-99905bacace8aed42b16d43f0f04cae996cb971c/> upgrade bstr to 1.0.1
<csr-id-e91c301342d44cff35ebe12fba4ec10afb4a1922/> replace quick-error with this-error
<csr-id-12589cc6f08e4d7aabae30bcdadaa0c2b4850229/> adapt to changes in git-url and use BString to represent URLs.
They can contain paths, which is why String can't repsent a URL
losslessly.
For HTTP urls these are ultimately UTF-8 strings though.
client::fetch_pack() isn't worth it after all.
The overhead required to make it work isn't worth the logic we are
enabling. Instead, it's OK to re-implement custom logic on the consumer
side based on this one.<csr-id-5f2276b63129163096be3cb229864fc589348da8/> don't enforce V2 as protocol, but smoothly downgrade like git does. For backward compatibility the shared handshake implementation allows the transport to control which protocol versions it wants to support to allow optiomizing for one special case, namely to prevent it to read all V1 refs on old servers but abort instead, closing the connection without delay.
Now we leave this feature for custom transports (who usually come with custom servers) and instead support fallbacks to other protocols if the server demands it.
<csr-id-a8727824a4c38b27d6ad7c73ccaf7a45839c0aa9/> don't pass 'include-tag' as argument by default. This flag always has to be added by the caller based on configuration.
<csr-id-24000fa7ad4607c23f6a4fb4d84d2c85d96ee01f/> don't post packfile-uris capability unless we are able to make use of it.
Turns out that this option can be rejected by a server that advertises
it, so definitely needs more work to make it work.
<csr-id-806b8c2ef392137f3a6ebd0f28da2a3a07a9f3eb/> Parse refs from bytes, not from String. The latter can cause issues around illformed UTF-8 which wouldn't bother git either.
This comes at the expense of not parsing line by line anymore, but instead reading as fast as possible and parsing afterwards.
Performance wise I think it doesn't matter, but it will cause more memory to be used. If this ever becomes a problem, for example during pushes where we are stuck with V1, we can consider implementing our own streaming appreach that works with packet lines instead - they are just not exposed here even though they could.
<csr-id-d7f62b441700c6d3526517c8c4f369cb9a72c102/> support keepalive packets. Keepalive packets are side-band only empty datalines that should just be ignored. This is now happening, allowing longer git operations to work as they will send keepalive packets every 5 seconds, and previously we would choke on it.
Note that empty datalines are never send otherwise, making it a previously unused marker that can safely be skipped.
<csr-id-266395e18d7cf754f51355098c84fd1c969fc972/> Link up Io error as source for error chaining; add Debug to client::fetch::Response
<csr-id-c77bd7a01820110154f2c66cd954c1ccfff173c1/> '(null)' symref targets are turned into direct refs instead… …because that's what 'git' would do if it would care enough. On the client side this means one has to deal with detached heads and it's obvious that these are detached. It's not clear anymore why this is the case, and probably it's good to hide it as the current git behaviour is accidental and may change in future, and do so in a way we predict.
There is the possibility that git would abort the entire fetch/upload-pack operation, but that's already handled correctly by our implementation as well as we understand ERR messages in packet lines.
<csr-id-4b8abb0e8a5326662f36b88f04681bdd0eaa8079/> display the underlying permission denied error as source when failng handshake due to authentication.
<csr-id-5a50d9599f820237866928df6d24a196a9b86fe3/> fetch::Arguments::use_include_tag() allows to signal include-tag.
One can also check for its availability using fetch::Arguments::can_use_include_tag().
Further there was a bugfix that assues V1 capabilities are correctly interpreted to support include-tag.
<csr-id-1c0a6c0edaca4063129c3b06638629b7af17a64c/> due to more specific errors one can differentiate if remote authentication failed repeatedly.
<csr-id-2363bcbd3207d1d16f2f95fbd20a7d7715b92240/> some errors support is_spurious() to tell if retrying is possible.
<csr-id-68c65a9f8b3927d454164a6f72167b47c0facee5/> expose futures_lite for convenience in downstream crates.
<csr-id-aed93d22d7a7faf4d60f1f603830c882175cbcb6/> Allow defaulting fetch::handshake::Outcome.
This is useful in conjunction with std::mem::take().
<csr-id-0bcb2fd4d5d8692a0e91c70bcbcbff9dff60442f/> fetch::Arguments::is_empty() to help decide if arguments should be sent at all.
Furthermore, the Debug trait was added.
<csr-id-31a7089f2583832727e2175ada6fb5c30c3beebe/> make some private methods public to give callers more flexibility. This allows to implement the fetch-negotiation part oneself and break free from constraints of the delegate.
<csr-id-744ed03cf6648e258affab62ef39ffad75c65397/> add client::fetch_pack() allowing to fetch a pack after a handshake.
<csr-id-eaff67c14366f149ccca346acb46af12531a24e6/> helper::main to easily create credential helper implementations
<csr-id-5ba9e1d20a8d523571a153f9f4e3e1a5285335b5/> provide a function to gracefully shut donw a fetch transport
<csr-id-b1c40b0364ef092cd52d03b34f491b254816b18d/> use docsrs feature in code to show what is feature-gated automatically on docs.rs
<csr-id-517677147f1c17304c62cf97a1dd09f232ebf5db/> pass --cfg docsrs when compiling for https://docs.rs
<csr-id-d6b4878d9832a0279e0dd19c1ca520a282289e69/> re-export maybe_async That way, API users can also provide dynamically sync or async APIs.
<csr-id-d2de51d65f9b4ab895e19cc1b307e42a9bb4bbd8/> add fetch::refs() method to invoke ls-refs for V2 and parse the result
<csr-id-35d17b4ea80be611607faa774d1ce0ee9c5000f2/> factor fetch handshake into fetch::handshake() function
<csr-id-0826cc92717faceff62df48a6e86fbb7ca6e90f5/> in-manifest and in-lib feature documentation
prepare_ls_refs in fetch::refs() into FnOnce.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
Clippy helped 29 times to make code idiomatic.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
e695eda)0c81769)a517e39)c1f3c9d)7f52823)145103d)4a9a05f)f536bad)a0bc98c)2f75db2)e1861ca)58ab2ae)c857d61)f1fa6dd)6b5c394)9d6f263)719b6bd)2f43a54)f293b63)6776a3f)07aa1bc)84cb256)42c977f)fetch::Ref::unpack() returns Option<oid>. (cd867ad)unborn ls-refs capability if server supports it. (02e37f0)b593806)prodash v21 (a0655dc)306ebef)d7f62b4)fetch::Arguments::is_empty() (df36ede)Debug to client::fetch::Response (266395e)fetch::handshake::Outcome. (aed93d2)fetch::Arguments::is_empty() to help decide if arguments should be sent at all. (0bcb2fd)31a7089)&dyn Any instead of unspecified serialization format, as it's the right way. (779eefe)git-transport (e842843)client::fetch_pack() isn't worth it after all. (f87b7eb)client::fetch_pack() allowing to fetch a pack after a handshake. (744ed03)c3e4b2a)wait-for-done (02245a6)prepare_ls_refs in fetch::refs() into FnOnce. (3a38d1b)45394d5)4720666)git-refspec (ffa24a1)fetch::Ref::unpack() returns &BStr instead of &BString as ref name. (91f193f)fetch::Ref::unpack() now returns the peeled object as well. (d2c772e)fetch::Ref::path to fetch::Ref::full_ref_name. (bab5860)bstr to 1.0.1 (99905ba)32758e8)git-credentials (27c9da5)08c1287)helper::main to easily create credential helper implementations (eaff67c)git-credentials (33f1347)git-credentials (fe1a06d)git-credentials (40cc1dc)077ab57)5ba9e1d)d6b4878)a6105cb)fetch::refs() function in fetch() (37504e6)fetch::refs() method to invoke ls-refs for V2 and parse the result (d2de51d)41a7391)fetch() method (aaa1680)quick-error with this-error (e91c301)fetch::handshake() function (35d17b4)1c5f561)e55b43e)git-transport (2141585)git-url and use BString to represent URLs. (12589cc)caa7a1b)oid type (3930a6f)be84b36)ca78d15)accf89d)a3f2816)4805cfc)packfile-uris capability unless we are able to make use of it. (24000fa)rust-version to 1.64 (55066ce)8c0bca3)7fc00f8)59e9fac)48f5bd2)a5869e0)41d57b9)e313112)6efd0d3)6ccc88a)c9275b9)git-testtools to gix-testtools (b65c33d)git-pack to gix-pack (1ee81ad)git-odb to gix-odb (476e2ad)git-index to gix-index (86db5e0)git-diff to gix-diff (49a163e)git-commitgraph to gix-commitgraph (f1dd0a3)git-mailmap to gix-mailmap (2e28c56)git-discover to gix-discover (53adfe1)git-chunk to gix-chunk (59194e3)git-bitmap to gix-bitmap (75f2a07)git-protocol to gix-protocol (823795a)git-protocol to gix-protocol (9a35a90)git-refspec to gix-refspec (c958802)git-revision to gix-revision (ee0ee84)git-transport to gix-transport (b2ccf71)git-credentials to gix-credentials (6b18abc)git-prompt to gix-prompt (6a4654e)git-command to gix-command (d26b8e0)git-packetline to gix-packetline (5cbd22c)git-worktree to gix-worktree (73a1282)git-hashtable to gix-hashtable (26a0c98)git-worktree to gix-worktree (108bb1a)git-url to gix-url (b50817a)git-date to gix-date (9a79ff2)git-attributes to gix-attributes (4a8b3b8)git-quote to gix-quote (648025b)git-config to gix-config (3a861c8)git-ref to gix-ref (1f5f695)git-lock to gix-lock (2028e78)git-tempfile to gix-tempfile (b6cc3eb)git-object to gix-object (fc86a1e)git-actor to gix-actor (4dc9b44)git-validate to gix-validate (5e40ad0)git-hash to gix-hash (4a9d025)git-features to gix-features (e2dd68a)git-glob to gix-glob (35b2a3a)git-sec to gix-sec (eabbb92)git-path to gix-path (d3bbcfc)git-config-value to gix-config-value (622b3e1)109f434)1ecfb7f)c196d20)7c846d2)1e544e8)39ed9ed)bac57dd)1fea18f)5b5b380)93bef97)b93f0c4)b34c9fe)ffb5b6a)4381a03)e0b12fe)5ac9fbe)30d8ca1)4b8abb0)08ec3a9)68ce15d)5afa7f5)e6b9906)7114bbb)5f2276b)c57bdde)083909b)fetch::Arguments::use_include_tag() allows to signal include-tag. (5a50d95)a872782)94750e1)1c0a6c0)70ccbb2)is_spurious() to tell if retrying is possible. (2363bcb)git-transport (527c62e)eb4c5f0)eca6705)dadd896)Fixture implementation for async. (b583c2a)7717170)9d8e32d)806b8c2)git-transport (49461b1)6b9632e)7893502)bcd9654)0abab7d)b2c301e)e4648f8)0e4462d)3d8fa8f)0c253b1)fe5721f)665b53e)b5c316e)fetch::refs(…, protocol, …) to the crate root as ls_refs(…). (09070a7)fetch::Command into the crate root. (35f7b4d)fetch::agent|indicate_end_of_interaction to crate root (a03f8f6)handshake(…) is now generalized to support git-receive-pack as well. (a3bcf82)611a139)7691353)f4ff821)0c9c48b)futures_lite for convenience in downstream crates. (68c65a9)git-transport (b46e3bb)git-transport (f88569b)git-transport (226f33a)'static (68dc86f)fetch::agent() returns agent string only; fetch() takes agent name as parameter. (d05b0b8)aab278f)fetch::agent() now returns the agent name, fetch::agent_tuple() returns specific key-value pair. (f957d9a)d071583)423af90)5406630)04cfa63)c4e6849)def53b3)bc9c780)104d922)d232567)702a161)f47c891)3c49400)82fd251)25a7726)f5c36d8)29a043b)3773b92)fd14489)c9eda72)535e967)5c05198)9aa1d3d)1d4600a)1f6e5ab)5869e9f)da0716f)bc64b96)cef0b51)85a3bed)c2660e2)cfa1440)4974eca)39d585d)e2ee3de)31c2351)b1c40b0)One column per quarter.