A Project is one repository plus everything Coroid needs to operate within it: build and test commands, context, policies and settings.
Create one from Projects → New, selecting a repository from a connected provider. If the expected repository is missing, see Connect your code.
What happens upon creation
Coroid clones the repository and analyses it to identify languages and frameworks, how it builds, how its tests run, and whether it can be containerised.
Check the result. See Build and test configuration — this is the configuration upon which everything else depends.
What a Project encompasses
| Area | What it covers |
|---|---|
| Repository | Base branch, branch behaviour — see Repository and branch settings |
| Build and test | How the Project compiles and verifies |
| Context | Documents, policies and references read by the agents |
| Quality | Which policy and gates apply |
| Test targets | Environments and accounts for browser testing |
| Discoveries | What Coroid identified in the codebase |
| Viability | File-size and pattern health indicators |
One Project per repository
Do not assign two Projects to the same repository to represent two workstreams. Use plans, sprints or lanes for that — see Tasks, plans, sprints and lanes — so both streams share one view of the code, one set of conventions and one context.
For a system spanning multiple repositories, create a Project for each. Coroid can then coordinate work across them.
Scratch and preview Projects
For experiments and throwaway work, a scratch Project keeps unwanted elements out of your actual Projects. See Preview and scratch Projects.
Deleting
Deleting a Project removes its configuration, context and history from Coroid. It does not affect your repository — branches and pull requests Coroid created remain in your provider, under your control.
Deleted Projects can be recovered for a period before permanent removal occurs. Retention is determined by your organisation's settings — see Data retention.