Development record
abcd build next --max 0 is read as no count at all: NextOptions.Max is 0 when the flag is not given, so an explicit --max 0 continues a live series (exit 0, a series move) and gives a single pick otherwise, while the refusal of a negative --max says a run count is '1 or more'. A person who types --max 0 is neither refused nor told it meant nothing. Found by the ruthless reviewer of fix/build-next-followups.
issueresolvedminoriss-2610121210280182
abcd build next --max 0 is read as no count at all: NextOptions.Max is 0 when the flag is not given, so an explicit --max 0 continues a live series (exit 0, a series move) and gives a single pick otherwise, while the refusal of a negative --max says a run count is '1 or more'. A person who types --max 0 is neither refused nor told it meant nothing. Found by the ruthless reviewer of fix/build-next-followups.
Frontmatter
| id | iss-2610121210280182 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2610121210280182-abcd-build-next-max-0-is-read-as-no.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-261025221434293734-build.md:210-212 lists the series refusals without --max 0, which iss-2610121210280182 made a refusal at the pick stage (commands/build.md:274-277).