Repository
In CellRepo, a repository is used to track one biological asset over time.
Most users can think of a repository as representing: - one strain - one construct - one plasmid - one cell line - or one engineered biological entity
A repository has its own history and records how that asset changes.
What a repository represents
A repository represents one thing, not a collection.
For example, a repository might represent: - ΔldhA knockout strain (E. coli MG1655) - Plasmid pLAC-OPT-v1 - CHO cell line – stability testing
Each of these would normally be tracked in its own repository.
Repositories are where traceability actually happens.
What a repository is not
A repository is not: - a project - a folder of unrelated assets - a single data file - a one-time record
If you want to group multiple assets together, you are likely thinking about a project, not a repository.
(See Project if you want to revisit this distinction.)
How repositories are used
Once a repository exists, you use it to: - record the current state of the asset - document changes over time - attach files, sequences, or notes - understand how and why the asset evolved
Changes are recorded using commits.
(See Commit for how this works in practice.)
When should you create a new repository?
You should create a new repository when:
- a new biological asset is created
- an asset becomes important enough to track properly
- you want a clear, independent history for something
For example: - a new strain derived from an existing one - a new plasmid variant - a cell line that will be maintained long-term
If two assets can change independently, they usually deserve separate repositories.
How repositories fit into projects
Repositories always live inside a project.
For example:
Organisation: NovaSyn Bio Lab
Project: Lactate production optimisation in E. coli
Repositories inside this project might include: - ΔldhA knockout strain (E. coli MG1655) - Plasmid pLAC-OPT-v1 - Parental MG1655 strain
The project provides context.
Repositories provide traceability.
Repository history
Each repository has its own history, made up of commits.
This history allows you to: - see how the asset changed - understand when decisions were made - identify who contributed - demonstrate provenance and ownership
History is never overwritten.
If something changes, a new commit records that change.
Naming repositories
Clear repository names make long-term use much easier.
Good examples: - “ΔldhA knockout strain (E. coli MG1655)” - “Plasmid pLAC-OPT-v1” - “CHO cell line – stability phase”
Avoid: - “Strain 1” - “New version” - “Final construct”
Good names help collaborators and future you understand what the repository represents without opening it.
Visibility and access
Repositories inherit visibility from their parent project.
That means: - you usually don’t need to configure access at creation time - permissions can be adjusted later if needed
For more detail, see
Visibility and access.
If you’re unsure how to structure repositories
It’s normal to feel unsure about whether something should be a new repository or an update to an existing one.
If in doubt: - start with separate repositories for distinct assets - keep histories simple and focused - adjust structure later if patterns emerge
CellRepo is designed to support restructuring without losing history.
Getting help
If you’re unsure whether something should be tracked as a separate repository, or how to structure assets within a project, you don’t need to decide alone.
You can contact us at
📧 support@cellrepo.com
We’re happy to help you map repositories to real lab scenarios.