diff options
| author | ewy <ewy0@protonmail.com> | 2026-04-14 20:16:02 +0200 |
|---|---|---|
| committer | ewy <ewy0@protonmail.com> | 2026-04-14 20:16:02 +0200 |
| commit | bff532551a14969e5c8732f13836ace7cc262a6f (patch) | |
| tree | 7ac1fa21c09f3f622a5e15176815bd91b6692fe1 | |
| parent | c94018702c9ff22a7d5e2206ccb1435c198f28f8 (diff) | |
add more doccies
| -rw-r--r-- | README.md | 4 |
1 files changed, 4 insertions, 0 deletions
@@ -24,9 +24,13 @@ running `pik` in any repository will index its own file-based task system, as we bear in mind scripts will always run in the project directory, not in the `.pik` folder. +## <span style="color: green">killer</span> features + pik comes equipped with a tui that allows for target browsing and invoking. open it by running `pik`. the output also gently reminds you how to run the invocation next time! +pik remembers your projects and you can invoke stuff almost anywhere. to view everything pik knows, try `pik -a`! + ## current features * run targets by their approximate name: `pik build` will trigger `.pik/build.sh`, or `.pik/build.py`, or `make build` |
