adjust to renaming of git-ref to gix-ref

CHANGELOG.md

@@ -796,7 +796,7 @@ A first usable version of `gix` to make using `gitoxide` from your applications
 * Packs are now reproducible by default, which means that the same tip will always generate a pack with the same hash. This may be a desirable property for some kinds of packs, but not for others which is why it can be turned off for a considerable speed boost.
 * `gix-tempfile` crate
 * `gix-lock` crate
-* `git-ref` crate with complete loose-ref, packed-ref and transaction support.
+* `gix-ref` crate with complete loose-ref, packed-ref and transaction support.
 
 
 ### Performance

Cargo.toml

@@ -103,7 +103,7 @@ document-features = { version = "0.2.0", optional = true }
 
 [profile.dev.package]
 gix-object = { opt-level = 3 }
-git-ref = { opt-level = 3 }
+gix-ref = { opt-level = 3 }
 #git-pack = { opt-level = 3 }
 gix-hash = { opt-level = 3 }
 gix-actor = { opt-level = 3 }
@@ -132,7 +132,7 @@ members = [
     "git-url",
     "gix-hash",
     "gix-validate",
-    "git-ref",
+    "gix-ref",
     "git-command",
     "git-config",
     "gix-config-value",
@@ -185,7 +185,7 @@ members = [
     "git-diff/tests",
     "git-pack/tests",
     "git-index/tests",
-    "git-ref/tests",
+    "gix-ref/tests",
     "git-config/tests",
     "git-traverse/tests",
 ]

Makefile

@@ -138,7 +138,7 @@ check: ## Build all code in suitable configurations
 unit-tests: ## run all unit tests
 	cargo test --all
 	cd gix-features && cargo test && cargo test --all-features
-	cd git-ref/tests && cargo test --all-features
+	cd gix-ref/tests && cargo test --all-features
 	cd git-odb && cargo test && cargo test --all-features
 	cd gix-object && cargo test && cargo test --features verbose-object-parsing-errors
 	cd git-pack/tests && cargo test --features internal-testing-to-avoid-being-run-by-cargo-test-all \

README.md

@@ -44,7 +44,7 @@ Documentation is complete and was reviewed at least once.
 
 * [git-mailmap](https://github.com/Byron/gitoxide/blob/main/crate-status.md#git-mailmap)
 * [git-chunk](https://github.com/Byron/gitoxide/blob/main/crate-status.md#git-chunk)
-* [git-ref](https://github.com/Byron/gitoxide/blob/main/crate-status.md#git-ref)
+* [gix-ref](https://github.com/Byron/gitoxide/blob/main/crate-status.md#gix-ref)
 * [git-config](https://github.com/Byron/gitoxide/blob/main/crate-status.md#git-config)
 * [gix-config-value](https://github.com/Byron/gitoxide/blob/main/crate-status.md#gix-config-value)
 * [gix-glob](https://github.com/Byron/gitoxide/blob/main/crate-status.md#gix-glob)

STABILITY.md

@@ -57,7 +57,7 @@ The following schematic helps to visualize what follows.
     ║    │ │  gix-hash   │   │  gix-actor  │ │    ║   
     ║    │ └─────────────┘   └─────────────┘ │    ║  │
     ║    │ ┌─────────────┐   ┌─────────────┐ │    ║   
-    ║    │ │   git-ref   │   │ git-config  │ │    ║  │
+    ║    │ │   gix-ref   │   │ git-config  │ │    ║  │
     ║    │ └─────────────┘   └─────────────┘ │    ║   
     ║    │ ┌─────────────┐   ┌─────────────┐ │    ║  │
     ║    │ │ gix-object  │   │  gix-lock   │ │    ║   
@@ -98,8 +98,8 @@ Released plumbing crates are marked with major version number 1 or above, for ex
 
 Breaking changes are collected and may be released no more often than every 4 weeks by incrementing the major version number.
 
-For example, `git-odb` and `git-ref` both have breaking changes, where `git-odb`'s change is on August 1st and `git-ref`'s dependent change
-is on September 10th. `git-odb`'s breaking change can be released earliest on September 1st, whereas `git-ref` can be released earliest at October 10th.
+For example, `git-odb` and `gix-ref` both have breaking changes, where `git-odb`'s change is on August 1st and `gix-ref`'s dependent change
+is on September 10th. `git-odb`'s breaking change can be released earliest on September 1st, whereas `gix-ref` can be released earliest at October 10th.
 
 If there are additional breaking changes without a release, these push back the earliest release date accordingly.