@goodfoot/git-mesh 1.0.68 → 1.0.70
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +16 -0
- package/man/git-mesh.1 +5 -4
- package/package.json +6 -6
package/README.md
ADDED
|
@@ -0,0 +1,16 @@
|
|
|
1
|
+
# git mesh
|
|
2
|
+
|
|
3
|
+
`git mesh` tracks implicit semantic dependencies in a git repository — line-range or whole-file anchors that participate in a coupling no schema, type, or test enforces. Each mesh names its anchors, carries a `why` sentence defining the subsystem they collectively form, and surfaces drift via `git mesh stale` when those anchors diverge from their anchored state.
|
|
4
|
+
|
|
5
|
+
The primary CLI surface lives in `src/cli/mod.rs`. Run `git mesh --help` or `git mesh stale --help` for flag reference.
|
|
6
|
+
|
|
7
|
+
### Upgrading from the sqlite cache
|
|
8
|
+
|
|
9
|
+
The trail cache now lives at `<common_dir>/mesh/cache/v1/` as a BLAKE3-keyed content-addressed filesystem store. The previous sqlite-backed cache at `<common_dir>/mesh/cache/mesh_cache.sqlite` (or `<git_dir>/mesh/cache/mesh_cache.sqlite` on older per-worktree installations), along with its `-shm` and `-wal` companions, is unused and can be removed with a single `rm -f <common_dir>/mesh/cache/mesh_cache.sqlite*` (and the `<git_dir>` variant if present). Nothing reads those files anymore; `git mesh doctor --gc-trail-cache` operates only on the new store.
|
|
10
|
+
|
|
11
|
+
## Profiling
|
|
12
|
+
|
|
13
|
+
Perf investigation tooling is documented in [`./docs/profiling.md`](./docs/profiling.md):
|
|
14
|
+
|
|
15
|
+
- **Flame graph capture** — `perf record` + `inferno-flamegraph` recipe for identifying hot functions.
|
|
16
|
+
- **`--perf-trace <path>`** — opt-in per-anchor wall-clock CSV emitter for `git mesh stale`; CSV schema, usage constraints, and quick analysis snippets are documented there.
|
package/man/git-mesh.1
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
.ie \n(.g .ds Aq \(aq
|
|
2
2
|
.el .ds Aq '
|
|
3
|
-
.TH git-mesh 1 "git-mesh 1.0.
|
|
3
|
+
.TH git-mesh 1 "git-mesh 1.0.70"
|
|
4
4
|
.ie \n(.g .ds Aq \(aq
|
|
5
5
|
.el .ds Aq '
|
|
6
6
|
.SH NAME
|
|
@@ -45,8 +45,9 @@ If the relationship has changed, update the why with
|
|
|
45
45
|
.B git mesh why
|
|
46
46
|
before re-anchoring.
|
|
47
47
|
.PP
|
|
48
|
-
Meshes are stored
|
|
49
|
-
.IR refs/meshes/v1
|
|
48
|
+
Meshes are stored in a catalog tree at
|
|
49
|
+
.IR refs/meshes/v1/catalog
|
|
50
|
+
as individual entries using a zero-copy archive format,
|
|
50
51
|
so they travel with
|
|
51
52
|
.B git fetch
|
|
52
53
|
and
|
|
@@ -140,7 +141,7 @@ Print this message or the help of the given subcommand(s)
|
|
|
140
141
|
.ie \n(.g .ds Aq \(aq
|
|
141
142
|
.el .ds Aq '
|
|
142
143
|
.SH VERSION
|
|
143
|
-
v1.0.
|
|
144
|
+
v1.0.70
|
|
144
145
|
.SH EXAMPLES
|
|
145
146
|
Anchor a new mesh alongside a code change:
|
|
146
147
|
.PP
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@goodfoot/git-mesh",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.70",
|
|
4
4
|
"bin": "bin/git-mesh",
|
|
5
5
|
"man": [
|
|
6
6
|
"man/git-mesh.1"
|
|
@@ -23,11 +23,11 @@
|
|
|
23
23
|
"scripts/postinstall.js"
|
|
24
24
|
],
|
|
25
25
|
"optionalDependencies": {
|
|
26
|
-
"@goodfoot/git-mesh-darwin-arm64": "1.0.
|
|
27
|
-
"@goodfoot/git-mesh-darwin-x64": "1.0.
|
|
28
|
-
"@goodfoot/git-mesh-linux-arm64": "1.0.
|
|
29
|
-
"@goodfoot/git-mesh-linux-x64": "1.0.
|
|
30
|
-
"@goodfoot/git-mesh-win32-x64": "1.0.
|
|
26
|
+
"@goodfoot/git-mesh-darwin-arm64": "1.0.70",
|
|
27
|
+
"@goodfoot/git-mesh-darwin-x64": "1.0.70",
|
|
28
|
+
"@goodfoot/git-mesh-linux-arm64": "1.0.70",
|
|
29
|
+
"@goodfoot/git-mesh-linux-x64": "1.0.70",
|
|
30
|
+
"@goodfoot/git-mesh-win32-x64": "1.0.70"
|
|
31
31
|
},
|
|
32
32
|
"repository": {
|
|
33
33
|
"type": "git",
|