Details how users can submit patch requests using `pr.pico.sh`
without needing to fork the repository or use `git send-email`.
Also clarifies that the example configuration file generation is
optional.
@@ -35,7 +35,7 @@ mv planning-mcp-server ~/.local/bin # assuming ~/.local/bin is in your shell's P
## Configuration
-Generate an example configuration file:
+Generate an example configuration file (optional):
```bash
planning-mcp-server --generate-config
@@ -141,6 +141,36 @@ Task IDs are deterministically generated based on the task title and description
**Important**: This server currently uses in-memory storage only. All goals and tasks are lost when the server restarts. Session management and persistence are planned for future releases.
+
+## Collaboration
+
+Patch requests are in [amolith/llm-projects] on [pr.pico.sh]. You don't need a
+new account to contribute, you don't need to fork this repo, you don't need to
+fiddle with `git send-email`, you don't need to faff with your email client to
+get `git request-pull` working...
+
+You just need:
+
+- Git
+- SSH
+- An SSH key
+
+```sh
+# Clone this repo, make your changes, and commit them
+# Create a new patch request with
+git format-patch origin/main --stdout | ssh pr.pico.sh pr create amolith/llm-projects
+# After potential feedback, submit a revision to an existing patch request with
+git format-patch origin/main --stdout | ssh pr.pico.sh pr add {prID}
+# List patch requests
+ssh pr.pico.sh pr list amolith/llm-projects
+```
+
+See "How do Patch Requests work?" on [pr.pico.sh]'s home page for a more
+complete example workflow.
+
+[amolith/llm-projects]: https://pr.pico.sh/r/amolith/llm-projects
+[pr.pico.sh]: https://pr.pico.sh
+
## License
AGPL-3.0-or-later