Skip to main content

Work on code and version control

KAIZEN integrates with Git-based version control systems to provide a seamless process from visual service design to code generation, branching, and collaborative development. This integration allows your team to generate backend and frontend code directly from KAIZEN designers, manage it across branches, and push changes to a shared repository within the platform.

Prerequisites

Before working with code and version control in KAIZEN, ensure the following:

  • Git is installed on your local machine. For setup instructions, refer to Set up the tools.
  • A Git provider is connected to your KAIZEN environment. Refer to this article to configure this connection to a Git hosting service (e.g., GitLab), so that repositories can be created and managed in KAIZEN.

Version control process

The typical process for code and version control in KAIZEN follows these steps:

  1. Settings: Set up the Git connection and configure your preferences. Refer to Settings for Git.

  2. Initialise: Create a repository for your service in the connected Git provider. This is a one-time setup per service. Refer to Initialise the Git repository.

  3. Manage Branch: Create and switch between branches to organise your development, testing, and release work. Refer to Manage branches.

  4. Design frontend and backend: Use the App Designer and Service Designer to visually design the application UI and services.

  5. Generate code: Generate BE (backend Spring Boot/Java) or FE (frontend ReactJS) code from your designs. You can download the code as a zip file or push it directly to Git. Refer to Generate the backend code and Generate the frontend code.

  6. Push Project: Commit your changes with a descriptive message and push them to the remote repository for collaboration and CI/CD pipelines. Refer to Push project.

  7. Merge Config: Merge configuration changes between branches. Refer to Merge configurations.

  8. Edit Token: Manage the Git access token used for authentication. Refer to Edit token.

Last updated on 20 May 2026