A common question is how Kleeen manages changes to a product in the authoring tool and work developers have already done to custom css or widgets and end points that are already wired.
Referencing the diagram above you can see that much of the workflow is the same when a human developer checks in code as when the Kleeen Authoring Tool checks in code using GitHub. Much like a human developer files are checked in incrementally and files Kleeen has not changed will not be updated. In the case that you have made changes to a folder Kleeen is also publishing changes to, you will manage this as you do today as if two human developers made changes. You will review the changes and accept, merge, and reject them following your normal devops procedures.
At Kleeen, we know this process works because the Kleeen Authoring Tool that is used by our customers today is built with that same tool. Updates to the product are handled by a process like the one outlined above.
If you need any help managing code management, please reach out to firstname.lastname@example.org, and we will be happy to help.