Managing Version Control
One of the important features of developing and application with Kleeen is that Kleeen will function in your development operations (devops) process just like a human developer would. A key component of this integration into devops is GitHub. GitHub is a tool that will allow you to easily manage version control issues. Used correctly, GitHub allows developers to collaborate and work on code for the same application while minimizing issues with asynchronous work. GitHub provides a nice overview of this process in the video below.
How Does Kleeen Leverage GitHub?
The simplest explanation of the way Kleeen leverages GitHub is that code updates from Kleeen will be managed as a Pull Request, often called a PR, and you will need to review and accept the changes before the code is available to your application. This article from GitHub's documents explains PRs well. This means that you can develop custom pieces of your application and integrate endpoints without fear that Kleeen will disturb this work. Your human developers will continue to work on the pieces of your application they need to code and Kleeen will check in new code as new features are released and you make updates to your application. If you are not ready for a feature Kleeen has released simply don't accept the pull requests for that piece until you are ready for them.
If you examine Kleeen's repository structure in most cases you will work in folders labeled as custom. Kleeen working asynchronously with your team will not modify the code you merge into these folders. These folders will be where you hook up to endpoints, customize styling, and develop pieces you indicate would be custom in Kleeen. Working in this fasion will prevent conflicts and allow Kleeen to be a highly productive member of your development team.
Any Questions? If so, please reach out to us at Support@Kleeen.Software.