clawdbot cli to spawn watcher to synchronize workspace files to a git repo
Basically what I describe in this post
https://x.com/onusoz/status/2008538728180941238
Could be customized, not everyone has to do it the way I described. But I found this workflow especially useful
- Choose one branch, always re-create/delete and merge it (need to enable deleting merged branches on repo settings on github)
- Could customize for people who don't use github
Let's discuss here, I can then create a more fleshed out issue on github later
https://x.com/onusoz/status/2008538728180941238
Could be customized, not everyone has to do it the way I described. But I found this workflow especially useful
- Choose one branch, always re-create/delete and merge it (need to enable deleting merged branches on repo settings on github)
- Could customize for people who don't use github
Let's discuss here, I can then create a more fleshed out issue on github later
Onur Solmaz (@onusoz)
.@clawdbot workspace and memory files can be version-controlled!
In our pod, inotify triggers a watcher script every time there is a change to workspace folder, to sync these files to our monorepo. It then goes through the same steps:
- Create zeno-workspace branch if doesn't
In our pod, inotify triggers a watcher script every time there is a change to workspace folder, to sync these files to our monorepo. It then goes through the same steps:
- Create zeno-workspace branch if doesn't
X
โข1/6/26, 1:58 PM
