Skip to content

Working With someli-mono-repo

Rule of thumb

Do not edit code here. This repo is a snapshot, not a source of truth.

What this repo can be used for

Use case OK? Why
Cross-cutting grep across BE+FE ✅ Single tree is convenient
Reading code for orientation ✅ Same caveat as below — code may be stale
Running it locally to reproduce a bug ⚠ Only if you're explicitly investigating a regression that happened around the snapshot date. Otherwise use the canonical repos.
Making changes and committing ❌ Changes will be lost on the next snapshot refresh (and never auto-deployed). Edit the canonical repo.
Cherry-picking commits from this repo ❌ Snapshot commits are not meaningful diffs — they're bulk "move" or "merge" operations.
Pointing CI / deploy automation at this repo ❌ The deploy pipelines live in the canonical repos; nothing here triggers a build.

If you've already started editing here

  1. Save your diff (git diff > /tmp/my-change.patch).
  2. Reset the snapshot (git restore .).
  3. Re-apply the patch in the canonical repo (cd ../someli-api && git apply /tmp/my-change.patch, or pick out the changed files and edit them by hand if the patch doesn't apply cleanly because the snapshot was stale).
  4. Open the PR from the canonical repo, not from here.

If you've been asked to refresh this snapshot

There is no documented automated process. The pattern observable in git log is:

  1. From the snapshot root, clear backend/ and frontend/.
  2. Copy from the latest canonical sources (with --exclude=.git --exclude=node_modules etc.).
  3. Commit on a per-side branch (be-main or fe-main).
  4. Merge the per-side branches back into main.

Before doing this, talk to whoever owns the snapshot's downstream consumers to make sure you're not breaking something that depends on the snapshot's specific commit.

  • The newer someli-project/ repo is the same idea applied to all six canonical repos (app pair + designer pair + admin pair). For most use cases of "I want a single tree", someli-project is the better target. See someli-project/README.md.