@open-tomato/rafa 0.22.0 → 0.23.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 +11 -1
- package/dist/cli.js +13512 -12330
- package/dist/{index-e30zazs6.js → index-ehsb7198.js} +9623 -7982
- package/dist/{index-gzr2gtmh.js → index-rw7tb99r.js} +1448 -1973
- package/dist/index.js +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -348,13 +348,23 @@ from GitHub Issues:
|
|
|
348
348
|
machine-specific failures a run meets stay off your public tracker.
|
|
349
349
|
Specs in an epic may not carry two `epic:` labels; `rafa issue ready`
|
|
350
350
|
refuses the second one.
|
|
351
|
+
- **Boards and switching.** Most projects stay on one board. A project
|
|
352
|
+
with several teams can hold one board per team, each with its own
|
|
353
|
+
owner and owned folders listed in `Owner:` and `Owns:` lines, and tied
|
|
354
|
+
to the repository's `CODEOWNERS` file. `rafa switch <n>` moves to that
|
|
355
|
+
board's epic and position, `rafa board list` shows all boards, and
|
|
356
|
+
`rafa status` prints where you stand. A switch made by hand re-homes; pass
|
|
357
|
+
`--no-rehome` to keep your home and go back to it later. The position
|
|
358
|
+
file `.rafa/position.json` holds your current place, where you were, and
|
|
359
|
+
where you came from — the same two-slot pattern as `cd -` and
|
|
360
|
+
`git checkout -`, plus a home anchor.
|
|
351
361
|
- **Other trackers.** GitHub Issues is what works today. Linear support
|
|
352
362
|
is being ported from the project rafa grew out of, as an optional
|
|
353
363
|
add-on in a later version. For anything else, open or upvote a request
|
|
354
364
|
in [the issues](https://github.com/open-tomato/rafa/issues).
|
|
355
365
|
|
|
356
366
|
The full guide, with the spec template explained, a prompt for drafting
|
|
357
|
-
a spec, epics and every gate in order, is
|
|
367
|
+
a spec, epics, boards and every gate in order, is
|
|
358
368
|
[docs/specs-and-roadmap.md](docs/specs-and-roadmap.md).
|
|
359
369
|
|
|
360
370
|
## From a checkout
|