Cloning Git Applications
Cloning brings an application that already exists in a Git repository into your workspace. It is how a second developer gets a copy of work someone else started, how you recover an application after clearing the local datastore, and how you connect to a repository that already has history.
Before you begin
- The repository must already contain an application, with at least one commit. If it is empty, create the application instead. See Creating a Git-Enabled Application.
- Git credentials with read access to the repository.
Cloning an application
- In the Applications panel, select the + icon, then select Create.
- On Choose Application Type, select Clone from git.
- Enter a Name for the imported application.
- Copy the remote repository's URL and paste it into the Remote Url field.
- Select the Multi module repository checkbox if the repository holds several applications. Name the application exactly as its folder is named in the repository, so Koodisi can locate the right module.
- Optionally enter a Description.
- Provide your Git credentials. For guidance on the options, see Creating a Git-Enabled Application.
- Select Create.
How you know it worked
Koodisi confirms the application was cloned, and it appears in the Applications panel. Open it and select the Version Control icon — the panel shows the checked-out branch and the repository's commit history on the Commits tab.
The clone checks out the repository's default branch. To work on another branch, select Fetch, then check out the branch you want from Remote on the Branches tab.
When it does not work
| Symptom | Cause | What to do |
|---|---|---|
Application clone failed. Existing application data was not changed. | The clone could not complete. Your existing applications are untouched. | Verify the remote URL and the credential, then retry. |
Application cloned, but workflow validation failed. | The clone succeeded, but the cloned workflows have validation errors. | The application is present. Open the workflows and fix the reported errors. |
| The credential is rejected | The token is expired, or lacks access to the repository. | Update the credential. See Troubleshooting Guide. |
Cannot find HEAD | The repository setup is incomplete, or the local Git metadata is corrupted. | Export the local datastore, clear it, and clone again. See Managing the Local Datastore. |
| The application is missing from the branch you checked out | In a multi-module repository, an application may exist on some branches and not others. | Select a branch that contains the application from the Active branch list. |
Avoiding merge conflicts once cloned
Koodisi does not resolve merge conflicts — that happens in your Git provider. A few habits keep them rare:
- Use the Description fields to document and track your work.
- Keep the team aware of which tasks are complete.
- If several people work on one branch, keep everyone in sync with the latest changes.
- Use branching to isolate work rather than sharing a branch.
For the full model, see Parallel Development with Multiple Developers. For recovery when a conflict does occur, see Handling Merge Conflicts.
Next steps
- Using Git with Applications — working the cloned application
- Git Workflow for Development — organizing your branches