Repositories
Register the repositories CodeLantern works in and tell each one which project-management provider its work lives in.
Connecting a provider tells CodeLantern it's available. A repository configuration tells it which provider each repository's work actually lives in. You manage this from the Repositories screen in the portal.
Point each repository at the right provider
Every repository CodeLantern works in gets a mapping. The PM and SCM sides are configured independently, so a repository can mix providers:
- A GitHub-only team points its repositories at GitHub for both PM and SCM.
- An Azure DevOps team points its repositories at Azure Boards for PM and Azure Repos for SCM — the Boards project need not be the same project that holds the repo.
- A team using Linear points its repositories at Linear for PM, with GitHub or Azure Repos for SCM.
- Mixed setups work too — e.g. Azure Boards for PM with GitHub for SCM.
When a skill runs against a repository, it follows that repository's configuration to know where to find issues and where to open pull requests.
Adding a repository
From Repositories, choose Add Repository, pick the repo, choose its PM provider, and select the specific project its issues live in.
The repository then shows as Active with its mapping. That mapping lets a skill read the right issue and open the pull request in the right place. It is also the check skills run before they act, which is why you configure it before running the workflow.
Next steps
Integrations
Connect your organization to GitHub, Azure DevOps, or Linear so CodeLantern skills can read and write your issues, pull requests, and source.
Analytics
A live view of the work across your connected repositories: how your knowledge base is growing, how fast issues move, and how the tools are used.