2. Connect a repository

A repository — a module, in Kodel’s vocabulary — is what agents read, search and change. A project can hold several; one of them is primary.

Connect it

On the project page press Connect repository and fill in:

• Repository URL — https://github.com/org/repo.git or git@github.com:org/repo.git. The name and slug are filled in from the address.
• Default branch — the branch that gets cloned and indexed.
• Access — Public for open repositories, otherwise a token, an SSH key or a username and password. Credentials are stored encrypted.
• Primary module of this project — leave it checked for your first repository. Steps that need code, but are not told which repository to use, fall back to the primary one.

Test connection verifies that the address is reachable before you commit to it; Connect starts the first clone.

Tip

If the default branch you typed does not exist, the platform detects the real one during the first clone and corrects itself — type main, get master, no error.

Wait for the first index

The status goes from Checking… to Connected, and the page fills in: indexed files, repository size, last checked, and the list of branches with their latest commits.

Indexing is what lets agents search the code by meaning instead of grepping blindly, so give it a moment on a large repository.

Branches and tasks

Later, when a pipeline runs on a task, it works in a run branch named after the task — kodel/wip/DEV-1. It is created from the repository’s development branch, or from the default branch when no separate development branch is set, and you can override the base per task.

Next

Now the interesting part: design a pipeline.