One thing I feel like we should add for automation...
# proj-automation
l
One thing I feel like we should add for automations: “sync to git” functionality. In this case, all automations on a particular VM would be synced to a git repository, so any time the automations change in the VM or in git, they would be auto-updated in the other. The reason why this would be helpful is that it would provide more visibility, controllability, and versioning of the automations. Right now on a VM it’s hard to see both the current state of the automations, and how they have changed over time.
Overleaf has this functionality, and it can be pretty handy.
h
I like that a lot. I also have been thinking about backups for canvas configuration. Once you have everything all set up its a pain if you need to redo it all.
Do you think a user should define the repo individually or should we think about a canvas-wide git syncing location for other things like extensions (skills+plugins)
l
I think the user should define the repo, or maybe even directory within a repo
Oh, sorry, when you say “user”, I mean that one setting per agent server, so one agent server will have a single list of automations and a single github repo or directory
h
So then the singular backend (the active agent-server) would have a git repo where that backend could sync things to
w
Very much agree!
This has been bugging me
I also have a sort of prototype here
👀 2
l
Here’s an issue for tracking: github.com/OpenHands/automation/issues/300
🙌 2