hyper-pm 0.1.5 → 0.1.6
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.
- package/README.md +8 -0
- package/dist/index.cjs +1261 -1118
- package/dist/main.cjs +1261 -1118
- package/package.json +3 -3
package/README.md
CHANGED
|
@@ -40,6 +40,14 @@ These apply before any subcommand (for example `hyper-pm --format text epic read
|
|
|
40
40
|
|
|
41
41
|
## Commands
|
|
42
42
|
|
|
43
|
+
### Work item display numbers
|
|
44
|
+
|
|
45
|
+
Each epic, story, and ticket has a durable ULID `id` plus a per-type **`number`**: a small positive integer (separate counters for epics, stories, and tickets). List JSON includes `number` on each row; full `read` JSON includes it on the record.
|
|
46
|
+
|
|
47
|
+
Any CLI flag that accepts a work item **`--id`** (or a parent like `--epic`, `--story`, or ticket list filters that take ids) also accepts that item’s **`number`** when it is written as an all-digit token (for example `ticket read 3` after you confirm ticket `3` in `ticket read` list output). Resolution tries the ULID/id string first, then a unique numeric match. If two items share the same `number` after a bad merge, numeric lookup is ambiguous and the command fails until the JSONL conflict is fixed.
|
|
48
|
+
|
|
49
|
+
Parallel offline edits can still assign the same next `number` on different branches; resolving that is the same class of problem as other JSONL merge conflicts.
|
|
50
|
+
|
|
43
51
|
### `init`
|
|
44
52
|
|
|
45
53
|
Create or adopt the orphan data branch and write `.hyper-pm/config.json`.
|