@goodfoot/git-mesh 1.0.26 → 1.0.29
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/man/git-mesh.1 +7 -7
- package/package.json +6 -6
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.29"
|
|
4
4
|
.ie \n(.g .ds Aq \(aq
|
|
5
5
|
.el .ds Aq '
|
|
6
6
|
.SH NAME
|
|
@@ -16,16 +16,16 @@ line ranges (or whole files), in code or prose, that no schema, type, or test
|
|
|
16
16
|
enforces.
|
|
17
17
|
Each
|
|
18
18
|
.B mesh
|
|
19
|
-
anchors the participating
|
|
19
|
+
anchors the participating anchors and carries a durable
|
|
20
20
|
.I why
|
|
21
|
-
\[em] one prose sentence that names the relationship the anchored
|
|
21
|
+
\[em] one prose sentence that names the relationship the anchored set holds
|
|
22
22
|
and survives a rewrite of either side.
|
|
23
23
|
.PP
|
|
24
24
|
The standing question at commit time: did this change create or rely on a
|
|
25
25
|
coupling that is not visible from the lines themselves?
|
|
26
26
|
.PP
|
|
27
27
|
.B Writing the why.
|
|
28
|
-
Name the relationship the
|
|
28
|
+
Name the relationship the anchors hold in one prose sentence, written so it
|
|
29
29
|
survives a rewrite of either side.
|
|
30
30
|
Describe the relationship in role\-words (\(lqthe doc,\(rq \(lqthe parser,\(rq
|
|
31
31
|
\(lqthe runbook,\(rq \(lqthe migration\(rq) rather than repeating filenames.
|
|
@@ -64,7 +64,7 @@ Bare invocations:
|
|
|
64
64
|
List every mesh in the repository.
|
|
65
65
|
.TP
|
|
66
66
|
.BI git\ mesh\ <name>
|
|
67
|
-
Show one mesh (
|
|
67
|
+
Show one mesh (anchors, why, config).
|
|
68
68
|
.RE
|
|
69
69
|
.ie \n(.g .ds Aq \(aq
|
|
70
70
|
.el .ds Aq '
|
|
@@ -92,7 +92,7 @@ git\-mesh\-rm(1)
|
|
|
92
92
|
Stage anchors to remove on the next mesh commit
|
|
93
93
|
.TP
|
|
94
94
|
git\-mesh\-why(1)
|
|
95
|
-
Read or stage the mesh\*(Aqs why —
|
|
95
|
+
Read or stage the mesh\*(Aqs why — a one\-sentence definition of the subsystem, flow, or concern the anchors collectively form
|
|
96
96
|
.TP
|
|
97
97
|
git\-mesh\-commit(1)
|
|
98
98
|
Resolve staged operations and write a mesh commit
|
|
@@ -132,7 +132,7 @@ Print this message or the help of the given subcommand(s)
|
|
|
132
132
|
.ie \n(.g .ds Aq \(aq
|
|
133
133
|
.el .ds Aq '
|
|
134
134
|
.SH VERSION
|
|
135
|
-
v1.0.
|
|
135
|
+
v1.0.29
|
|
136
136
|
.SH EXAMPLES
|
|
137
137
|
Anchor a new mesh alongside a code change:
|
|
138
138
|
.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.29",
|
|
4
4
|
"bin": "bin/git-mesh",
|
|
5
5
|
"man": [
|
|
6
6
|
"man/git-mesh.1"
|
|
@@ -21,11 +21,11 @@
|
|
|
21
21
|
"scripts/postinstall.js"
|
|
22
22
|
],
|
|
23
23
|
"optionalDependencies": {
|
|
24
|
-
"@goodfoot/git-mesh-darwin-arm64": "1.0.
|
|
25
|
-
"@goodfoot/git-mesh-darwin-x64": "1.0.
|
|
26
|
-
"@goodfoot/git-mesh-linux-arm64": "1.0.
|
|
27
|
-
"@goodfoot/git-mesh-linux-x64": "1.0.
|
|
28
|
-
"@goodfoot/git-mesh-win32-x64": "1.0.
|
|
24
|
+
"@goodfoot/git-mesh-darwin-arm64": "1.0.29",
|
|
25
|
+
"@goodfoot/git-mesh-darwin-x64": "1.0.29",
|
|
26
|
+
"@goodfoot/git-mesh-linux-arm64": "1.0.29",
|
|
27
|
+
"@goodfoot/git-mesh-linux-x64": "1.0.29",
|
|
28
|
+
"@goodfoot/git-mesh-win32-x64": "1.0.29"
|
|
29
29
|
},
|
|
30
30
|
"repository": {
|
|
31
31
|
"type": "git",
|