From d3b1408c931f1ab4435ddb704086557040d8b85c Mon Sep 17 00:00:00 2001 From: Amolith Date: Wed, 14 May 2025 14:06:06 -0600 Subject: [PATCH] docs: update collaboration instructions Improve the explanation of the patch request workflow and add a link to the pico.sh patch request homepage for further details. --- README.md | 20 +++++++++++++++++--- 1 file changed, 17 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 360f1897969f74e25a130fb6169d5fa750b1f9a3..15c71bf23cb7c62dc25f496e2f6e6d70fd23f5dc 100644 --- a/README.md +++ b/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