Development record
launch archive without --verify refuses a dirty working tree (exit 2), but the verb's own help does not say so: the --verify flag help and the Long text in internal/surface/cli/archive.go are silent on it, so the generated docs/reference/cli/commands.md does not carry the refusal either. A local 'launch archive --out d' on a dirty tree exits 2 with an error its --help never mentioned. Remedy: state the refusal in the --verify help and the Long text, and regenerate the reference.
issueresolvedminoriss-2609251940377887
launch archive without --verify refuses a dirty working tree (exit 2), but the verb's own help does not say so: the --verify flag help and the Long text in internal/surface/cli/archive.go are silent on it, so the generated docs/reference/cli/commands.md does not carry the refusal either. A local 'launch archive --out d' on a dirty tree exits 2 with an error its --help never mentioned. Remedy: state the refusal in the --verify help and the Long text, and regenerate the reference.
Grounds
- pursued: launch archive --help and docs/reference/cli/commands.md name the exit-2 dirty-tree refusal without --verify; a help or reference page that omits it, or a reference drifting from the command tree, would show it wrong
Frontmatter
| id | iss-2609251940377887 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2609251940377887-launch-archive-help-omits-its-dirty-tree.md
open on GitHub ↗ · commit history ↗