@boxes-dev/dvb-runtime 1.0.1075 → 1.0.1077

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.
@@ -12,9 +12,12 @@ gitSigning:
12
12
  for hardware-backed keys (YubiKey, FIDO, smartcard) or agent-only SSH
13
13
  keys — `run` reports if the copy can't work, in which case fall back to
14
14
  `create` or `skip`.
15
- - `create`: prepare a signing key locally and upload it to the Template box. The user must
16
- register its public key with their Git host for commits to show as
17
- verified.
15
+ - `create`: prepare a boxes.dev signing key locally and upload it to the
16
+ Template box. An existing local signing key is not required. Set Git
17
+ `user.name` and `user.email` in the repo first. Setup will use `gpg.format`
18
+ (`openpgp` by default, or `ssh`) without changing local signing settings.
19
+ The user must register its public key with their Git host for commits to
20
+ show as verified.
18
21
  - `skip`: unsigned commits from the Template box.
19
22
 
20
23
  How to decide (ask, don't guess): check whether the user signs commits at
@@ -23,6 +26,10 @@ repo — then confirm their preference. Users who don't sign locally almost
23
26
  always want `skip`. Users who do sign usually want `copy` unless their key
24
27
  is hardware-backed.
25
28
 
29
+ If the user wants signing on the Template box but does not sign locally,
30
+ choose `create`. When a project mixes signed and unsigned repos, setup will
31
+ keep signing limited to the repos that already sign.
32
+
26
33
  This is a one-line decision in the manifest; the machinery (key detection,
27
34
  staging, warnings) runs during `run` and surfaces problems in its output.
28
35