From 8681fbdd61d56f3047cecf030ae2178b319ece8b Mon Sep 17 00:00:00 2001 From: Sp5rky Date: Thu, 17 Jul 2025 19:10:35 -0600 Subject: [PATCH] Updated Services (markdown) --- Services.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Services.md b/Services.md index 10e8655..419ff9c 100644 --- a/Services.md +++ b/Services.md @@ -175,7 +175,7 @@ Service Code. > Please be careful with who you trust and what you run. The users you collaborate with on Service > code could update it with malicious code that you would run via unshackle on the next call. -## Forking +### Forking If you are collaborating with a team on multiple services then forking the project is the best way to go. @@ -207,7 +207,7 @@ If you are new to `git` then take a look at [GitHub Desktop](https://desktop.git > However, if the core project also has dependency changes your `uv.lock` changes will conflict and you > will need to learn how to do conflict resolution/rebasing. It is worth it though! -## Symlinking +### Symlinking This is a great option for those who wish to do something like the forking method, but may not care what changes happened or when and just want changes synced across a team.