Back to corpus
proposalbacklog referencescore 26

Git Synchronization Strategy

``` Main Repo (points to cc-studio.git) ❌ MISMATCHED │ ├── apps/ios/cc-handguard/.git # Separate repo ├── apps/web/cc-dashboard/.git # Separate repo (has remote) ├── apps/web/cc-studio/.git # Separate repo │ ├── core/cc-core/.git # Separate repo ├── core/cc-trajectory/.git # Separate repo (large, 4GB) │ └── [6 more nested repos inside trajectory] # Deep nesting │ └── backend/cc-mcs/.git # Likely exists ```

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

### Main Repository - **Current remote**: `https://github.com/Diomandeee/cc-studio.git` - **Issue**: Points to cc-studio but contains entire Computational Choreography project - **Recent commits**: Show submodule updates for cc-dashboard **Git is confused** because: 1. Your main repo remote is `cc-studio.git` (just one component) 2. But the repo contains the entire 17GB Computational Choreography project 3. You have nested repos that are **not configured as submodules** 4. Git sees these nested repos as "deleted files" (the `D` in git status) **Yes, it's a good idea** to keep everything in one repository using **Git Submodules**. **Benefits**: - ✅ Work on entire project in one place - ✅ Each component has its own repo (independent versioning) - ✅ Main repo tracks specific commits of each submodule - ✅ Easy to update individual components - ✅ Can open in one IDE/workspace **Challenges**: - ⚠️ Requires explicit submodule commands (`git submodule update`) - ⚠️ Collaborators need to know about submodules - ⚠️ Slightly more complex workflow

Promotion decision

What has to happen next

Keep as idea/proposal unless evidence and implementation anchors exist.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.