Skip to main content

Push project

After designing your application or configuring your service, you can commit your changes and push the generated code to the connected Git repository directly from KAIZEN. This process bundles code generation with version control, ensuring that every commit contains the latest generated code alongside your design definitions. This integration enhances the CI/CD pipeline by automating the process of committing and pushing changes, improving efficiency and collaboration.

Open the Push Project window

There are two methods to open the Push Project window:

  1. At the project toolbar, click the Git icon Git icon.

  2. Use one of the following methods to push changes to your project:

    From the dropdown menu, select Push Project.

    Push Project at project toolbar

    The Push Project window opens with the Branch dropdown at the top, allowing you to select the target branch before pushing.

  3. Provide details in the Push Project window.

  4. Click Ok to commit and push the selected items to the connected Git repository.

Push Project window

The Push Project window contains the following sections:

Branch

This dropdown appears only when you open the Push Project window at the project toolbar. Select the target branch to push your changes to.

note

The Branch field is required (marked with an asterisk).

Applications

The Applications table lists each application in the project. Select the checkbox next to an application to include it in the push.

ColumnDescription
NameThe name of the application.
Latest RevisionIndicates whether there are unpublished changes to the application.
Latest Published RevisionIndicates whether the latest revision has been published.
Code Generate VersionA dropdown to select the code generation version for the application.
HistoryClick the history icon to view previous push records for the application.

Services

The Services table lists each service in the project. Select the checkbox next to a service to include it in the push.

ColumnDescription
NameThe name of the service.
Service Layer ClassesA checkbox that indicates whether service layer classes are included.
Custom ConfigurationA checkbox that indicates whether custom configuration files are included.
KAIZEN VersionA dropdown to select the KAIZEN version for the service.
HistoryClick the history icon to view previous push records for the service.

Config

The Config table lists the configuration items in the project. Select the checkbox to include configuration in the push.

ColumnDescription
ConfigLists the configuration categories included in the push (e.g., User Domain, User Groups, Memberships, MasterCode, Navigator, Endpoint).
HistoryClick the history icon to view previous push records for configuration.

Comments

Enter a descriptive commit message. This field is required (marked with an asterisk).

View commit history

The Push Project window displays a History section that shows the commit history for each application and service. This allows you to track previous pushes and verify version details directly within the push workflow.

  1. Click the Git icon Git icon at the project level and select Push Project.

  2. In the Push Project window, scroll down to the History section. The history is displayed with tabs for each application component.

    The commit history table displays the following information for each entry:

    ColumnDescription
    Commit IDThe unique identifier for the commit.
    AuthorThe author associated with the Git token used for the connection.
    Commit ByThe system that performed the commit (for example, KAIZEN).
    StatusThe result of the commit operation (for example, Success).
    MessageThe commit message entered when pushing the code.
    Commit TimeThe date and time when the commit was made.
note

Commit history is branch-specific. Commits made on one branch are only visible within that branch and will not appear when viewing history from a different branch.

What happens when you commit and push

When you commit and push, KAIZEN pushes to the following under the connected Git repository:

RepositoryDescription
fe-<name>Frontend generated React code.
fe-<name>-definitionFrontend screen pages which store the JSON schema (JS definitions etc). This schema is rendered during runtime and on preview to load the page.
be-<name>Backend generated code.

Commit and push code to the repository

For more information on how to commit and push your code to the connected Git repository, refer to Generate frontend code and Generate backend code.

Last updated on 20 May 2026