Creating a Git-Enabled Application

A Git-enabled application stores its source in a Git repository, so your team can track changes, review work, and roll back. You can create one application per repository, or several applications inside one multi-module repository. Either way, Git is turned on while you create the application, and the repository details are supplied at the same time.

You can create Git-enabled applications in any workspace, or keep them all in a single workspace to simplify management.

Before you begin

• An empty Git repository. Koodisi treats a repository with existing history — including a readme-only repository — as content to be cloned rather than initialized. If yours already has commits, use Clone from git instead. See Cloning Git Applications.
• Git credentials for that repository: a username and a personal access token from your Git provider.
• Git control is available for orchestration applications. A bundle application cannot use Git, and the toggle reports Bundle applications can't be used with Git.

Creating a single Git-enabled application

1. Go to the Applications page, select the + icon, and select Create.

2. On Choose Application Type, select New Application.

3. Enter a Name.

4. Optionally select a template from Use template.

5. Leave Application Type (required) set to Orchestration. This is the default, and it is the type Git control supports.

6. Turn on Enable Git control. The Git settings appear.

7. Enter the Remote Url of your Git repository.

8. Leave Multi module repository cleared.

9. Provide the credentials for the repository, using one of three options:

   • Use Existing Credentials — select a saved credential from Credential Name. The associated username appears automatically. See Managing Credentials.
   • New Credentials — enter a name in Enter Credential Name, select the Git Provider hosting your repository, then enter the username and Personal Access Token. The credential is saved to the Credential Manager against your user, so it is not available to other users.
   • Continue Without Credential — do not save credentials in Koodisi. You are asked for them each time you run a Git command.

10. Select Create.

How you know it worked

The application appears in the Applications panel, and the Version Control icon becomes available in the right sidebar when the application is selected. Open it to see the Version Control panel, with the current branch at the top. See Using Git with Applications.

Your application content is not in the repository yet. Stage and commit it on the Changes tab — that first commit creates the branch.

Creating a multi-module application

A multi-module repository holds several applications, each in its own folder. The first time you create an application in one, that repository becomes the default location for the workspace's other multi-module applications, and the Remote Url is pre-filled from the workspace for subsequent applications.

To create an application inside a multi-module repository, follow the steps above with two differences:

• Select the Multi module repository checkbox.
• Enter the Remote Url of the shared repository, or accept the pre-filled workspace value.

info

Name the application in Koodisi exactly as its folder is named in the remote repository. The name is how Koodisi locates the application's module within the shared repository.

See Single vs. Multi-Module Repositories to decide which structure suits your project.

When it does not work

Symptom	Cause	What to do
The repository contains application content. Use Clone from Git instead.	The repository already holds an application.	Clone it instead of creating a new application.
Repository already has history, including README-only repositories. Use Clone from Git to preserve it.	The repository has commits — a readme is enough.	Use an empty repository, or clone.
The repository README conflicts with this application's documentation. Use an empty repository or Clone from Git as a new application.	The repository readme collides with the application's own documentation file.	Use an empty repository, or clone as a new application.
Bundle applications can't be used with Git	The application type is a bundle.	Create an orchestration application.
The Enable Git control toggle is missing	Git is not enabled for the workspace.	Check your workspace Git settings, or ask an administrator.

Next steps

• Using Git with Applications — committing, branching, and pushing
• Git Branching Policy — the naming rules your branches must follow
• The Development Lifecycle — the path from here to production