The artifact hash prefix 1433 is ambiguous and might mean any of the following:
1433996fd6e789148401428c389e902b4b254cedf9ad70b4c62a802c5e02718a -
- File
src/cmd/tracking.zig
— part of check-in
[10a1236a7a]
at
2026-08-17 19:28:13
on branch trunk
— -R: say which mistake was made, not 'no checkout here' (#97)
The discovery message tells the operator to name the repository with -R. For a -R failure that advises supplying the flag already supplied, and it reads the same whether the path was mistyped or simply holds no repository -- so a stale path in a script looked like a bug in the verb. Reported against tarball; every -R verb had it. One reporter, routed through all nine resolveRoot call sites; the no-flag discovery message is unchanged. (user: dmestas, size: 131631) [annotate] [blame] [check-ins using]
- File
src/cmd/tracking.zig
— part of check-in
[10a1236a7a]
at
2026-08-17 19:28:13
on branch trunk
— -R: say which mistake was made, not 'no checkout here' (#97)
1433b1181738eececb8fceca74d08a1fe13dbaad536ccec9be0e129d06198646 -
- File src/cli.zig — part of check-in [bb2f45e4ff] at 2026-08-29 19:21:14 on branch trunk — Prefixes resolve through aliases and name the shortest spelling that works; verb help lists its aliases (zit#170) (user: dmestas, size: 351452) [annotate] [blame] [check-ins using]