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,65 +0,0 @@
# -*- coding: utf-8 -*-
# Copyright 2026 Nexa Systems Inc.
# License OPL-1 (Odoo Proprietary License v1.0)
# Part of the Fusion Plating product family.
{
'name': 'Fusion Plating - Quality Bridge (EE)',
'version': '19.0.1.0.1',
'category': 'Manufacturing/Plating',
'summary': 'Enterprise bridge: mirrors Fusion Plating NCRs into Odoo EE '
'quality.alert for native dashboard integration. Auto-installs '
'when EE quality and fusion_plating_quality are both present.',
'description': """
Fusion Plating - Quality Bridge (Enterprise)
============================================
Part of the Fusion Plating product family by Nexa Systems Inc.
One-way sync from Fusion Plating NCRs to Odoo EE quality.alert records.
Shops on Odoo Enterprise running both modules continue to work primarily
in Fusion Plating's QMS (which is CE + EE compatible), while getting the
benefit of EE's native quality dashboards on the same data.
How it works
------------
* When a Fusion Plating NCR is created or updated, a mirrored
``quality.alert`` record is created (or updated) automatically.
* The sync is ONE-WAY - NCR is the source of truth. Changes made
directly to the EE quality.alert are NOT pushed back into the NCR.
* A dedicated "Plating Quality" team is created in the EE quality
module so mirrored alerts land in their own distinct team and do
not pollute the default quality dashboards.
* Per-NCR opt-out is available via the ``x_fc_auto_sync`` field.
Installation
------------
This module has ``auto_install = True``: it installs itself automatically
as soon as both ``fusion_plating_quality`` and ``quality`` (EE) are
present in the database. Community Edition users who do not have the EE
``quality`` module will never see this bridge - the Fusion Plating QMS
remains fully self-contained.
Copyright (c) 2026 Nexa Systems Inc. All rights reserved.
""",
'author': 'Nexa Systems Inc.',
'website': 'https://www.nexasystems.ca',
'maintainer': 'Nexa Systems Inc.',
'support': 'support@nexasystems.ca',
'license': 'OPL-1',
'price': 0.00,
'currency': 'CAD',
'depends': [
'fusion_plating_quality',
'quality',
],
'data': [
'security/ir.model.access.csv',
'data/quality_alert_team_data.xml',
'views/fp_ncr_views.xml',
],
'installable': True,
'application': False,
'auto_install': True,
}