@sacho/sacho-aarch64-apple-darwin 0.1.0-dev.0 → 0.1.0-dev.11

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.
Files changed (3) hide show
  1. package/README.md +19 -37
  2. package/package.json +2 -2
  3. package/sacho +0 -0
package/README.md CHANGED
@@ -18,7 +18,7 @@ towncrier assumes Python; changesets assumes an npm monorepo. Sacho is a single
18
18
  static binary with no runtime dependencies, usable in any repository regardless
19
19
  of language, and it does not even assume Git.
20
20
 
21
- [Sacho is opinionated.](./PHILOSOPHY.md) It enforces one fragment format,
21
+ [*Sacho is opinionated.*](./PHILOSOPHY.md) It enforces one fragment format,
22
22
  one output style, and one set of invariants. Configuration exists to describe
23
23
  your repository, not to customize the philosophy.
24
24
 
@@ -55,6 +55,16 @@ Without mise, npm, or Cargo, download the archive for your platform from
55
55
  [GitHub Releases]: https://github.com/dahlia/sacho/releases
56
56
 
57
57
 
58
+ Documentation
59
+ -------------
60
+
61
+ The [*Sacho documentation*] walks through adoption, everyday use, releases,
62
+ CI, and version-control integration. It also explains Sacho's core concepts and
63
+ provides complete command and configuration references.
64
+
65
+ [*Sacho documentation*]: https://sacho.dev/guide/getting-started
66
+
67
+
58
68
  How it works
59
69
  ------------
60
70
 
@@ -161,7 +171,8 @@ Version-control integration
161
171
  ---------------------------
162
172
 
163
173
  Sacho can enforce that commits changing configured source paths also carry a
164
- changelog fragment. Select the repository's VCS in *sacho.toml*:
174
+ changelog fragment. Select the repository's VCS and the paths to check in
175
+ *sacho.toml*:
165
176
 
166
177
  ~~~~ toml
167
178
  [vcs]
@@ -176,41 +187,6 @@ Git also supports `sacho check --staged`. The `none` preset explicitly skips
176
187
  VCS-backed checks while leaving fragment validation and changelog consistency
177
188
  checks enabled.
178
189
 
179
- Each preset supplies three subprocess commands. Repositories can override one
180
- command without repeating the other two:
181
-
182
- ~~~~ toml
183
- [vcs]
184
- preset = "git"
185
-
186
- [vcs.commands]
187
- message = ["my-vcs-wrapper", "message", "${commit}"]
188
- ~~~~
189
-
190
- The first array element is the executable and every remaining element is one
191
- literal argument; Sacho never invokes a shell. The commits command uses
192
- `${base}`, while changed-paths and message use `${commit}`. An overridden query
193
- is the complete query and does not invoke commands from its preset behind the
194
- scenes. The built-in Mercurial preset handles parent comparisons internally.
195
-
196
- The query output contracts are:
197
-
198
- - `commits` emits zero or more nonempty UTF-8 commit identifiers, oldest
199
- first and one per line. The final line may end in LF; CRLF is also
200
- accepted.
201
- - `changed-paths` emits concatenated NUL-terminated name-status records.
202
- Ordinary records are `A\0PATH\0`, `D\0PATH\0`, `M\0PATH\0`, or
203
- `T\0PATH\0`, where `T` denotes a file type change. Copy and rename records
204
- are `C[SIMILARITY]\0OLD_PATH\0NEW_PATH\0` and
205
- `R[SIMILARITY]\0OLD_PATH\0NEW_PATH\0`, where the optional similarity is a
206
- decimal percentage from 0 through 100. Status fields are UTF-8 and paths
207
- are nonempty repository-relative platform paths; path bytes need not be
208
- UTF-8 on Unix. Nonempty output ends in NUL. A copied or renamed fragment
209
- counts as new content only when similarity is present and below 100;
210
- omitting it does not satisfy fragment coverage.
211
- - `message` emits the complete UTF-8 commit message verbatim. Sacho does not
212
- trim it.
213
-
214
190
  `sacho init` installs Git merge attributes and drivers in Git repositories. In
215
191
  Mercurial repositories it installs an idempotent block in *.hg/hgrc* containing
216
192
  a successful-merge update hook and, when changelog materialization is enabled,
@@ -219,6 +195,12 @@ the changelog merge driver. These integrations invoke the executable that ran
219
195
  per-path merge-driver hook; after resolving a concurrent fragment merge, run
220
196
  `sacho sync --force`.
221
197
 
198
+ See [*CI and hooks*] for fragment coverage and [*Version control*] for preset,
199
+ merge-driver, and custom-query details.
200
+
201
+ [*CI and hooks*]: https://sacho.dev/guide/ci-and-hooks
202
+ [*Version control*]: https://sacho.dev/guide/version-control
203
+
222
204
 
223
205
  Etymology
224
206
  ---------
package/package.json CHANGED
@@ -1,10 +1,10 @@
1
1
  {
2
2
  "name": "@sacho/sacho-aarch64-apple-darwin",
3
- "version": "0.1.0-dev.0",
3
+ "version": "0.1.0-dev.11+f8249e8",
4
4
  "description": "The Sacho binary for aarch64-apple-darwin",
5
5
  "license": "GPL-3.0-only",
6
6
  "author": "Hong Minhee <hong@minhee.org>",
7
- "homepage": "https://github.com/dahlia/sacho",
7
+ "homepage": "https://sacho.dev/",
8
8
  "repository": {
9
9
  "type": "git",
10
10
  "url": "git+https://github.com/dahlia/sacho.git"
package/sacho CHANGED
Binary file