kenzuya/unshackle
1
0
Fork 1
mirror of https://github.com/unshackle-dl/unshackle.git synced 2026-03-12 17:39:01 +00:00
Code Issues Packages Projects Releases Wiki Activity

Updated Services (markdown)

Sp5rky
2025-07-17 19:10:35 -06:00
parent 42591c63b2
commit 8681fbdd61
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
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 > 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. > 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. 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 > 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! > 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 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. happened or when and just want changes synced across a team.