@obsfx/trekker 1.7.2 → 1.10.0
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 +30 -0
- package/dist/index.js +568 -274
- package/package.json +13 -2
package/README.md
CHANGED
|
@@ -41,6 +41,7 @@ My concerns about the future and security of that project led me here. Trekker i
|
|
|
41
41
|
|
|
42
42
|
What you get:
|
|
43
43
|
- Task and epic tracking with dependencies
|
|
44
|
+
- Ready command to find unblocked tasks and see what they unblock
|
|
44
45
|
- Full-text search across tasks, epics, subtasks, and comments
|
|
45
46
|
- Unified list view with filtering by type, status, priority, and custom sorting
|
|
46
47
|
- Optional kanban board UI available as a [separate package](https://github.com/obsfx/trekker-dashboard)
|
|
@@ -78,6 +79,12 @@ trekker dep add TREK-2 TREK-1
|
|
|
78
79
|
trekker dep add TREK-3 TREK-1
|
|
79
80
|
```
|
|
80
81
|
|
|
82
|
+
See what is ready to work on:
|
|
83
|
+
|
|
84
|
+
```bash
|
|
85
|
+
trekker ready
|
|
86
|
+
```
|
|
87
|
+
|
|
81
88
|
Update task status as you work:
|
|
82
89
|
|
|
83
90
|
```bash
|
|
@@ -142,6 +149,29 @@ trekker dep remove <task-id> <depends-on-id>
|
|
|
142
149
|
trekker dep list <task-id>
|
|
143
150
|
```
|
|
144
151
|
|
|
152
|
+
### Ready
|
|
153
|
+
|
|
154
|
+
Show tasks that are ready to work on — unblocked and in `todo` status. For each ready task, shows downstream dependents that will be unblocked once it is completed:
|
|
155
|
+
|
|
156
|
+
```bash
|
|
157
|
+
trekker ready
|
|
158
|
+
```
|
|
159
|
+
|
|
160
|
+
Example output:
|
|
161
|
+
```
|
|
162
|
+
2 ready task(s):
|
|
163
|
+
|
|
164
|
+
TREK-1 | P0 | Setup database
|
|
165
|
+
-> unblocks TREK-2 | todo | P1 | Build API layer
|
|
166
|
+
-> unblocks TREK-3 | todo | P1 | Build UI layer
|
|
167
|
+
TREK-4 | P2 | Write docs
|
|
168
|
+
```
|
|
169
|
+
|
|
170
|
+
Tasks are sorted by priority (critical first). A task is considered ready when:
|
|
171
|
+
- Status is `todo`
|
|
172
|
+
- It is a top-level task (not a subtask)
|
|
173
|
+
- All its dependencies are resolved (`completed`, `wont_fix`, or `archived`)
|
|
174
|
+
|
|
145
175
|
### Search
|
|
146
176
|
|
|
147
177
|
Full-text search across epics, tasks, subtasks, and comments using FTS5:
|