Skip to content

Track a new strain

This workflow shows how to use CellRepo to start tracking a new biological strain from scratch.

The goal is simple:

create a traceable, chronological record of how a strain comes into existence and evolves

You don’t need all data upfront.
You just need to start recording meaningful states.

When should you use this workflow?

Use this workflow when:

  • you create a new strain
  • you receive a strain from another lab
  • you start working on a biological asset you want to track properly

If the strain already exists and you are making changes, see
Update an existing strain.

What you will create

By the end of this workflow, you will have:

  • one project (context)
  • one repository (the strain)
  • one or more commits (its recorded states)

Step 1: Create or choose a project

Projects group related work.

Examples:

  • a research study
  • a grant
  • a collaboration
  • a PhD chapter

If you don’t already have one:

  • go to your dashboard
  • create a new project
  • choose appropriate visibility

(See: Create your first project if needed.)

Step 2: Create a repository for the strain

Each strain should have its own repository.

Think of the repository as:

the identity of the strain itself

When creating the repository:

  • use a clear, stable name
    (e.g. E. coli ΔlacZ, Yeast strain A1)
  • keep the description short and factual
  • don’t worry about filling everything perfectly

You can always refine later.

Step 3: Make the initial commit

The first commit answers one question:

What is this strain at the moment it enters my workflow?

Examples:

  • “Initial construction of strain”
  • “Strain received from collaborator”
  • “Baseline wild-type strain”

In this commit you might include:

  • origin information
  • construction method (if known)
  • any confirmed genotype or phenotype
  • notes about uncertainty

It’s okay if information is incomplete.

Step 4: Add data incrementally

As work progresses, create new commits when something meaningful changes.

For example:

  • transformation completed
  • genotype confirmed
  • sequencing results added
  • design decisions changed

Each commit becomes a checkpoint.

You are not editing the past — you are extending history.

Step 5: Use commit messages intentionally

A good commit message explains:

  • what changed
  • why it matters

Future-you (and collaborators) should be able to understand the history without asking questions.

Avoid vague messages like:

  • “update”
  • “final”
  • “fix”

What not to worry about

You do not need to:

  • upload all files immediately
  • structure everything perfectly
  • decide long-term naming conventions on day one

CellRepo is designed for real research workflows, not idealised ones.

Result: a traceable strain history

Once you’ve followed this workflow:

  • every change is recorded
  • ownership is clear
  • collaboration becomes easier
  • audits and reviews become trivial

You’ve turned a strain into a traceable asset.

Depending on what you want to do next: