docs: update collaboration instructions

Amolith created 5 months ago

Improve the explanation of the patch request workflow and add a link to the
pico.sh patch request homepage for further details.

Change summary

README.md | 20 +++++++++++++++++---
1 file changed, 17 insertions(+), 3 deletions(-)

Detailed changes

README.md

@@ -40,18 +40,32 @@ Point [Home Assistant's MCP integration] at the `/sse` endpoint.
 
 ## Collaboration
 
-Patch requests are all on [pr.pico.sh].
+Patch requests are in [amolith/lunatask-mcp-server] 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/lunatask-mcp-server
-# Submit a revision to an existing patch request with
+# After potential feedback, submit a revision to an existing patch request with
 git format-patch main --stdout | ssh pr.pico.sh pr add {prID}
 # List patch requests
 ssh pr.pico.sh pr list amolith/lunatask-mcp-server
 ```
 
-[pr.pico.sh]: https://pr.pico.sh/r/amolith/lunatask-mcp-server
+See "How do Patch Requests work?" on [their home page] for a more complete example
+workflow.
+
+[amolith/lunatask-mcp-server]: https://pr.pico.sh/r/amolith/lunatask-mcp-server
+[pr.pico.sh]: https://pr.pico.sh
 
 ## Models and prompts