docs(plugins): clarify the fork-and-PR publishing flow

This commit is contained in:
mauriceboe
2026-07-03 18:20:06 +02:00
committed by Maurice
parent 1cee4e93b1
commit a920c6f72a
+6 -1
View File
@@ -25,7 +25,12 @@ npx trek-plugin validate .
This runs the exact checks the registry CI runs — a local pass predicts a CI
pass.
## 4. Open a PR against the registry
## 4. Fork the registry and open a PR
You don't have write access to the registry, so **fork
[TREK-Plugins](https://github.com/mauriceboe/TREK-Plugins)** to your own account,
add your entry there, and open a pull request from your fork back to the
registry's `main` branch.
Add one file, `registry/plugins/<id>.json`: