Development record
34-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).
issueopenminoriss-2610252214342937
34-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).
Frontmatter
| id | iss-2610252214342937 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610252214342937-34-build-md-210-212-lists-the-series.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2610121210280182abcd 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.