Split 49 modules/suites into independent git repos; untrack from monorepo
Some checks failed
fusion_accounting CI / test (fusion_accounting_ai) (push) Has been cancelled
fusion_accounting CI / test (fusion_accounting_core) (push) Has been cancelled
fusion_accounting CI / test (fusion_accounting_migration) (push) Has been cancelled

Each top-level module/suite folder is now its own private repo on GitHub
(gsinghpal/<name>) and gitea (admin/<name>), with a fresh single initial
commit. The monorepo no longer tracks them (added to .gitignore + git rm
--cached); working-tree files are retained on disk and managed in their
own repos. The monorepo keeps shared root files (CLAUDE.md, docs/, scripts/,
tools/, AGENTS.md, WIP/obsolete dirs) and full history.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
gsinghpal
2026-06-07 01:54:34 -04:00
parent 2a7b315e98
commit a66cdefc01
6740 changed files with 51 additions and 1277207 deletions

View File

@@ -1,107 +0,0 @@
# Graph Report - /Users/gurpreet/Github/Odoo-Modules/fusion_accounting_documents (2026-04-22)
## Corpus Check
- 9 files · ~3,618 words
- Verdict: corpus is large enough that graph structure adds value.
## Summary
- 36 nodes · 44 edges · 11 communities detected
- Extraction: 89% EXTRACTED · 11% INFERRED · 0% AMBIGUOUS · INFERRED: 5 edges (avg confidence: 0.8)
- Token cost: 0 input · 0 output
## Community Hubs (Navigation)
- [[_COMMUNITY_Community 0|Community 0]]
- [[_COMMUNITY_Community 1|Community 1]]
- [[_COMMUNITY_Community 2|Community 2]]
- [[_COMMUNITY_Community 3|Community 3]]
- [[_COMMUNITY_Community 4|Community 4]]
- [[_COMMUNITY_Community 5|Community 5]]
- [[_COMMUNITY_Community 6|Community 6]]
- [[_COMMUNITY_Community 7|Community 7]]
- [[_COMMUNITY_Community 8|Community 8]]
- [[_COMMUNITY_Community 9|Community 9]]
- [[_COMMUNITY_Community 10|Community 10]]
## God Nodes (most connected - your core abstractions)
1. `TestDocumentToInvoice` - 11 edges
2. `AccountMove` - 3 edges
3. `DocumentsDocument` - 2 edges
4. `CreateInvoiceFromDocumentWizard` - 2 edges
5. `Tests for the documents.document <-> account.move bridge.` - 1 edges
6. `Reverse linkage from account.move back to source documents.` - 1 edges
7. `Bridge documents.document to accounting moves. Adds a Many2one link to the crea` - 1 edges
8. `Open the wizard to create a vendor invoice from this document.` - 1 edges
9. `Wizard to create a vendor invoice from a Documents document. The wizard creates` - 1 edges
## Surprising Connections (you probably didn't know these)
- None detected - all connections are within the same source files.
## Communities
### Community 0 - "Community 0"
Cohesion: 0.48
Nodes (2): TestDocumentToInvoice, TransactionCase
### Community 1 - "Community 1"
Cohesion: 0.33
Nodes (3): DocumentsDocument, Bridge documents.document to accounting moves. Adds a Many2one link to the crea, Open the wizard to create a vendor invoice from this document.
### Community 2 - "Community 2"
Cohesion: 0.4
Nodes (0):
### Community 3 - "Community 3"
Cohesion: 0.4
Nodes (2): AccountMove, Reverse linkage from account.move back to source documents.
### Community 4 - "Community 4"
Cohesion: 0.4
Nodes (2): CreateInvoiceFromDocumentWizard, Wizard to create a vendor invoice from a Documents document. The wizard creates
### Community 5 - "Community 5"
Cohesion: 0.67
Nodes (1): Tests for the documents.document <-> account.move bridge.
### Community 6 - "Community 6"
Cohesion: 1.0
Nodes (0):
### Community 7 - "Community 7"
Cohesion: 1.0
Nodes (0):
### Community 8 - "Community 8"
Cohesion: 1.0
Nodes (0):
### Community 9 - "Community 9"
Cohesion: 1.0
Nodes (0):
### Community 10 - "Community 10"
Cohesion: 1.0
Nodes (0):
## Knowledge Gaps
- **5 isolated node(s):** `Tests for the documents.document <-> account.move bridge.`, `Reverse linkage from account.move back to source documents.`, `Bridge documents.document to accounting moves. Adds a Many2one link to the crea`, `Open the wizard to create a vendor invoice from this document.`, `Wizard to create a vendor invoice from a Documents document. The wizard creates`
These have ≤1 connection - possible missing edges or undocumented components.
- **Thin community `Community 6`** (1 nodes): `__init__.py`
Too small to be a meaningful cluster - may be noise or needs more connections extracted.
- **Thin community `Community 7`** (1 nodes): `__init__.py`
Too small to be a meaningful cluster - may be noise or needs more connections extracted.
- **Thin community `Community 8`** (1 nodes): `__init__.py`
Too small to be a meaningful cluster - may be noise or needs more connections extracted.
- **Thin community `Community 9`** (1 nodes): `__init__.py`
Too small to be a meaningful cluster - may be noise or needs more connections extracted.
- **Thin community `Community 10`** (1 nodes): `__manifest__.py`
Too small to be a meaningful cluster - may be noise or needs more connections extracted.
## Suggested Questions
_Questions this graph is uniquely positioned to answer:_
- **Why does `TestDocumentToInvoice` connect `Community 0` to `Community 2`, `Community 5`?**
_High betweenness centrality (0.142) - this node is a cross-community bridge._
- **Why does `CreateInvoiceFromDocumentWizard` connect `Community 4` to `Community 2`?**
_High betweenness centrality (0.101) - this node is a cross-community bridge._
- **What connects `Tests for the documents.document <-> account.move bridge.`, `Reverse linkage from account.move back to source documents.`, `Bridge documents.document to accounting moves. Adds a Many2one link to the crea` to the rest of the system?**
_5 weakly-connected nodes found - possible documentation gaps or missing edges._